This bug will be used to track all packages that must be stabilized before GCC 4.6. - Please file a NEW bug for each package that needs to be stabilized and have it BLOCK this one. - The bug should be assigned to the maintainer of the package. Please do not CC gcc-porting - we get enough mail on these things. - DO NOT use this bug for any problems with GCC itself. Instead, file a NEW bug describing your issue and it will be assigned by a bug wrangler. Thanks.
A while back I went through the 4.6 tracker and made a list of broken packages and their first working versions. I only got about halfway through before I was distracted by something else but it should still help. https://overlays.gentoo.org/proj/gcc-porting/browser/STABLE-4.6
*** Bug 434676 has been marked as a duplicate of this bug. ***
*** Bug 444534 has been marked as a duplicate of this bug. ***
This one blocks bug 351648 (please add it to the list, thank you)
Are we ready to go on this?
Seems this bug is still being blocked by 346809
(In reply to comment #5) > Are we ready to go on this? +1 Apart from bug 401561 I don't see any obstacles
I heard that 4.5 was EOLed upstream. I don't mind pushing this through.
Arch ppl, please stabilize gcc-4.6.3. arm, please note bug #401561. I don't have arm hardware so we'll need some help with that bug.
amd64 stable
x86 stable
ppc stable
ppc64 stable
(In reply to comment #9) > Arch ppl, please stabilize gcc-4.6.3. arm, please note bug #401561. I > don't have arm hardware so we'll need some help with that bug. I just tested it (and noted results in the bug), I can't replicate the ICE, everything is fine. Can anyone from the arm arch team test and confirm my results?
ia64 stable
sparc stable
alpha stable
I've reverted alpha stabilization wrt bug 451680
(In reply to comment #9) > Arch ppl, please stabilize gcc-4.6.3. arm, please note bug #401561. I > don't have arm hardware so we'll need some help with that bug. @dirtyepic: seems we have a lot of boostrap comparison failures...So, if we want to keep gcc:4.6 stable I think we should filter the flags that produces this error, or at least add an ewarn. What do you think about?
(In reply to comment #19) > (In reply to comment #9) > > Arch ppl, please stabilize gcc-4.6.3. arm, please note bug #401561. I > > don't have arm hardware so we'll need some help with that bug. > > @dirtyepic: seems we have a lot of boostrap comparison failures...So, if we > want to keep gcc:4.6 stable I think we should filter the flags that produces > this error, or at least add an ewarn. What do you think about? Alternatively, maybe just have it append-flags -fno-omit-frame-pointer which is reported to work.
If you're talking about the pentium3 thing then it's on my todo list.
this one might block https://bugs.gentoo.org/show_bug.cgi?id=451920 for arm? hopefully it'll be stable there soon
here's one that arm-stabilization might depend on: https://bugs.gentoo.org/show_bug.cgi?id=452768
arm stable
Stable for HPPA.
sh stable
s390 stable
@alpha, since bug 454426 is fixed, how sounds stabilize?
(In reply to Raúl Porcel from comment #29) > alpha stable Actually I've reverted it because i think i didn't test it properly :)
After testing it correctly, alpha stable
See bug #467274.