This bug is used for the tracking of packages broken by the upcoming GCC 4.5 release, which has now entered the pre-release stage. - File a NEW bug for each issue and make it BLOCK this one. Assign these bugs to the maintainer of the package in question, NOT gcc-porting@g.o please. - Bugs filed without patches will be closed as INVALID. - Don't use this bug for issues in GCC 4.5 itself. File a new bug and assign it to the toolchain team. - Please keep this tracker free from comments. Discussion should take place on the relevant bugs.
Should bugs with new GCC features (such as -lto) be filed against this bug too?
- Don't use this bug for issues in GCC 4.5 itself. File a new bug and assign it to the toolchain team make it block bug #315377 as well.
Created attachment 233977 [details, diff] -
Comment on attachment 233977 [details, diff] - not here
Comment on attachment 233977 [details, diff] - I am very sorry for the misdirected attachment which was meant for another bug, of course.
Just a reminder @ALL: Please remember to send gcc-4.5 patches upstream Thanks
I just rebuilt some amd64 systems which have ~3200 packages installed on them (including most of sci-biology and sci-chemistry and grub-1.98) without issues. I'd say it's ready to be unmasked.
I second the motion. I have an Atom CPU which could benefit from an atom specific -march as mentioned in the feature list.
This has been unmasked for months now. It's not going into stable for quite a while yet.
Time to close this.