Skip to content
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] 3.6 release blockers #22748

Closed
zmodem opened this issue Jan 28, 2015 · 15 comments
Closed

[meta] 3.6 release blockers #22748

zmodem opened this issue Jan 28, 2015 · 15 comments
Assignees
Labels
bugzilla Issues migrated from bugzilla

Comments

@zmodem
Copy link
Collaborator

zmodem commented Jan 28, 2015

Bugzilla Link 22374
Resolution FIXED
Resolved on Mar 02, 2015 12:58
Version unspecified
OS All
Depends On #22434 #22607 #22631 #22742 llvm/llvm-bugzilla-archive#22373 #22749 #22779 #22868 #22875 #22879 #22880 #22881 #22924
CC @gruech
@zmodem
Copy link
Collaborator Author

zmodem commented Jan 28, 2015

assigned to @zmodem

@llvmbot
Copy link
Collaborator

llvmbot commented Feb 2, 2015

http://llvm.org/bugs/show_bug.cgi?id=22060 this may cause some PIC codes fail,works for 3.5, seems regression。

@maleadt
Copy link
Contributor

maleadt commented Feb 2, 2015

I've come across 2 regressions: http://llvm.org/bugs/show_bug.cgi?id=22405 prevents using PCH with 3.6 Support headers, and http://llvm.org/bugs/show_bug.cgi?id=22385 breaking RefactoringTool when rewriting sources in a subdirectory.

@rotateright
Copy link
Contributor

If it's not too late and there's no bot fallout in the near future, I think we should get r227983 ( http://llvm.org/viewvc/llvm-project?view=revision&revision=227983 ) into the branch.

It is effectively a reversion of r224330 ( http://llvm.org/viewvc/llvm-project?view=revision&revision=224330 ) and part of the fix for bug 22371.

@gruech
Copy link
Mannequin

gruech mannequin commented Feb 3, 2015

Maybe http://llvm.org/bugs/show_bug.cgi?id=22293 is for your list, it crashes the compiler.

@llvmbot
Copy link
Collaborator

llvmbot commented Feb 10, 2015

At risk of being a presumptuous ass, I'm adding 22506 and 22513 to the list here in case it missed anyone's radar. IMHO, 22506 definitely needs to be fixed; there was some discussion on IRC as to whether a bug which appears to only crop up with Polly (though it's not clear to me that its necessarily a Polly bug, per se) should be considered a release blocker, so (obviously) feel free to demote it if you see fit.

@llvmbot
Copy link
Collaborator

llvmbot commented Feb 10, 2015

Sorry, that last bit was in reference to 22513.

@zmodem
Copy link
Collaborator Author

zmodem commented Nov 26, 2021

mentioned in issue #22749

@maleadt
Copy link
Contributor

maleadt commented Nov 26, 2021

mentioned in issue #22779

@zmodem
Copy link
Collaborator Author

zmodem commented Nov 26, 2021

mentioned in issue #22868

@dotdash
Copy link
Contributor

dotdash commented Nov 26, 2021

mentioned in issue #22875

@markus-oberhumer
Copy link

mentioned in issue #22879

@llvmbot
Copy link
Collaborator

llvmbot commented Nov 26, 2021

mentioned in issue #22880

@dotdash
Copy link
Contributor

dotdash commented Nov 26, 2021

mentioned in issue #22881

@dotdash
Copy link
Contributor

dotdash commented Nov 26, 2021

mentioned in issue #22924

@llvmbot llvmbot transferred this issue from llvm/llvm-bugzilla-archive Dec 9, 2021
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bugzilla Issues migrated from bugzilla
Projects
None yet
Development

No branches or pull requests

6 participants