https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62077
--- Comment #55 from Venkataramanan <venkataramanan.kumar at amd dot com> --- Hi Richard, >> I don't see why we need to fix this for the 4.9 or 4.8 branch. It never >> worked there and another existing workaround is to configure with >> --enable-stage1-checking=release. Linaro releases are based GCC 4.9 and 4.8 branches and so we wanted to release GCC 4.9 compiler that would bootstrap LTO. So once we fix things in gcc 5.0, we will be back porting to 4.9 /4.8 branches ? Or we need to tell users that GCC 4.9 or GCC 4.8 will always need workarounds Regards, Venkat. -----Original Message----- From: rguenther at suse dot de [mailto:gcc-bugzi...@gcc.gnu.org] Sent: Monday, August 18, 2014 7:11 PM To: Kumar, Venkataramanan Subject: [Bug bootstrap/62077] --with-build-config=bootstrap-lto fails https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62077 --- Comment #54 from rguenther at suse dot de <rguenther at suse dot de> --- On Mon, 18 Aug 2014, venkataramanan.kumar at amd dot com wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62077 > > --- Comment #53 from Venkataramanan <venkataramanan.kumar at amd dot > com> --- Hi Richard, > > >> Well, it would be a workaround only. The real fix is to track down and > >> fix all remaining issues we have with regarding to IL differences caused > >> by collection changes. > > In your earlier comment you mentioned that > > > OTOH fixing that may not be suitable for the release branches, > > neither is passing fixed values for GC parameters. > > So for release branch 4.9 shall we go for this workaround patch ? I don't see why we need to fix this for the 4.9 or 4.8 branch. It never worked there and another existing workaround is to configure with --enable-stage1-checking=release. -- You are receiving this mail because: You are on the CC list for the bug.
