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

[llvm-gcc] [meta] Make llvm-gcc4 completely replace llvm-gcc3 #870

Closed
markus-oberhumer opened this issue Jan 21, 2005 · 6 comments
Closed

[llvm-gcc] [meta] Make llvm-gcc4 completely replace llvm-gcc3 #870

markus-oberhumer opened this issue Jan 21, 2005 · 6 comments

Comments

@markus-oberhumer
Copy link

@markus-oberhumer markus-oberhumer commented Jan 21, 2005

Bugzilla Link 498
Resolution FIXED
Resolved on Sep 26, 2007 01:36
Version trunk
OS All
Depends On llvm/llvm-bugzilla-archive#869 llvm/llvm-bugzilla-archive#870 llvm/llvm-bugzilla-archive#947 llvm/llvm-bugzilla-archive#1379

Extended Description

I've been playing with heavily templated C++ code (Boost MPL) over the last
weeks and am getting various compiler ICEs. While some of these may be actual
llvm bugs I think a number are inherited from the somewhat outdated C++ frontend
(I've personally reported a number of g++ bugs in the gcc bug database which are
fixed in the meantime).

While grepping over the llvm-gcc sources it seems that not too many files are
actually touched by llvm, and when they are they are usually nicely tagged, so
I'm asking if a re-merge with the current 3.4 CVS branch seems resonable.

I'm quite aware that such a merge is boring, cumbersome and error prone, but
with some fresh energy and some modern merge tools it should not be too hard.
The llvm test suite should catch most merge problems, and the reward would be a
huge number of gcc fixes (estimating several hundred of bugs, though llvm is not
affected by all of them).

Comments ?

Thanks,
Markus

@lattner
Copy link
Collaborator

@lattner lattner commented Jan 21, 2005

That would be wonderful, patches gladly accepted!!

-Chris

@lattner
Copy link
Collaborator

@lattner lattner commented Nov 11, 2005

I'm changing this to be a meta bug. All problems that are blocked by our current llvm-gcc are going to
be marked as depending on this bug.

-Chris

@lattner
Copy link
Collaborator

@lattner lattner commented Sep 26, 2007

llvm-gcc3 is dead

@lattner
Copy link
Collaborator

@lattner lattner commented Nov 27, 2021

mentioned in issue llvm/llvm-bugzilla-archive#869

@lattner
Copy link
Collaborator

@lattner lattner commented Nov 27, 2021

mentioned in issue llvm/llvm-bugzilla-archive#870

@nlewycky
Copy link
Contributor

@nlewycky nlewycky commented Nov 27, 2021

mentioned in issue llvm/llvm-bugzilla-archive#947

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

Successfully merging a pull request may close this issue.

None yet
3 participants