-
Notifications
You must be signed in to change notification settings - Fork 12.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[meta] 4.0.0 Release Blockers #30970
Comments
assigned to @zmodem |
Please merge the fix for bug 31606, e.g. r291955 ("Generalize our tentative DR resolution for inheriting copy/move constructors to better match the pre-P0136R1 behavior") |
It's on my list, Richard just wanted it to bake on trunk for a bit before we merge. Thanks. |
May I merge r292119 please? We hit this recently with -Wsystem-header builds, it's a left-over bug from the five-digit-revision age. |
r292244 is a fix for a recent regression reported on NetBSD, i.e. -march=native -mno-sse41 would assert for no good reason. May I merge it? |
OK to both. |
I've added bug 31685 so that we can merge the fix for bug 30543 |
Please merge the fix for bug 27685 - already fixed on master, but not on the branch |
I'm not sure if we want to consider bug 31756 a release blocker, as it requires xray to identify setups that inhibit the use of rdtscp. I've asked Dean to comment here about it. |
Bug 31547 is relatively serious for those of us who have to work with libgcc for compatibility reasons. It breaks e.g. building GNU sed 4.3 with clang on a Linux system using libgcc. IMO this should be fixed for the release. |
I'd like to request merging two revisions:
|
I think XRay bug 31756 should not be considered a release blocker. There's quite a bit of work to do to probe and work-around the lack of rdtscp, and I wouldn't want to be blocking the release contingent on that being addressed. |
Merged as r293298
r293289 |
Will llgo be released with 4.0 (It does have a release_40 branch and a 4.0.0rc1 tag, but isn't listed anywhere...)? If so, should add bug 31786 to the blockers -- the fixes attached there are needed to make llgo compile on Linux. |
I didn't tag or branch it, and I don't see any branch here: http://llvm.org/svn/llvm-project/llgo/branches/ I don't think llgo is part of the release process. |
I would like to nominate rL293230 for inclusion into LLVM 4.0 it is a small fix that allows LLVM to build with the Intel 2017 toolchain. |
I'd like to request that r292624 - "[mips] Fix debug information for __thread variable" |
I've replied on the commit email.
r293664
r293665. |
One of our users discovered a problem with SafeStack. I suspect it may be too late to get it fixed for 4.0, but added it to this tracking bug to ensure it won't get lost. |
It sounds like the revision that regressed that was in 3.9 too, so it's not a regression and too late for 4.0. I'll change it to be a 4.0.1 blocker instead. |
The release has shipped, so closing this. For 4.0.1 blockers, use llvm/llvm-bugzilla-archive#32061 . |
mentioned in issue #30974 |
mentioned in issue #30976 |
mentioned in issue #30986 |
mentioned in issue #30992 |
mentioned in issue #31021 |
mentioned in issue #31020 |
mentioned in issue #31033 |
mentioned in issue #31036 |
mentioned in issue #31037 |
Extended Description
This is the tracking bug for blockers of the 4.0.0 release.
The text was updated successfully, but these errors were encountered: