|
View:
New views
8 Messages
—
Rating Filter:
Alert me
|
|
|
Trunk is closed for LTO mergeI have started the final merge from the lto branch into trunk. Please
refrain from committing any changes until I open mainline again. Thanks. Diego. |
|
|
Re: Trunk is closed for LTO mergeDiego Novillo wrote:
> I have started the final merge from the lto branch into trunk. Please > refrain from committing any changes until I open mainline again. Will the merge allow lto by default (so that we do not have to specify --enable-lto) ? Or do we have to force it, like on the branch ? -- Toon Moene - e-mail: toon@... - phone: +31 346 214290 Saturnushof 14, 3738 XG Maartensdijk, The Netherlands At home: http://moene.org/~toon/ Progress of GNU Fortran: http://gcc.gnu.org/gcc-4.5/changes.html |
|
|
Re: Trunk is closed for LTO mergeOn Sat, Oct 3, 2009 at 10:13, Toon Moene <toon@...> wrote:
> Will the merge allow lto by default (so that we do not have to specify > --enable-lto) ? If the correct version is found, yes. This is the same behaviour that is implemented in the lto branch. > Or do we have to force it, like on the branch ? You never had to force it on the branch, either. The only reason I kept asking folks to force it was simply to make sure that 'configure' was finding the right libelf. If libelf is not installed and you force LTO, configure complains. Otherwise, configure silently disables LTO. Diego. |
|
|
Re: Trunk is closed for LTO mergeDiego Novillo wrote:
> On Sat, Oct 3, 2009 at 10:13, Toon Moene <toon@...> wrote: > >> Will the merge allow lto by default (so that we do not have to specify >> --enable-lto) ? > > If the correct version is found, yes. This is the same behaviour that > is implemented in the lto branch. > >> Or do we have to force it, like on the branch ? [ Never had to force it on the branch, either ] OK, So tomorrow I plan to svn up my gcc trunk, recompile it for C and Fortran, recompile our Weather Forecasting system with it, and see what happens (the compile of the Weather code doesn't use -flto yet, obviously. Thanks, -- Toon Moene - e-mail: toon@... - phone: +31 346 214290 Saturnushof 14, 3738 XG Maartensdijk, The Netherlands At home: http://moene.org/~toon/ Progress of GNU Fortran: http://gcc.gnu.org/gcc-4.5/changes.html |
|
|
Re: Trunk is closed for LTO mergeOn Sat, Oct 3, 2009 at 10:30, Toon Moene <toon@...> wrote:
> So tomorrow I plan to svn up my gcc trunk, recompile it for C and Fortran, > recompile our Weather Forecasting system with it, and see what happens (the > compile of the Weather code doesn't use -flto yet, obviously. Thanks, that would be great. Please file bugs you find with 'Component: lto' and 'Reported against: lto'. Fortran currently shows ~140 testsuite failures due to problems with whole-program mode. Thanks. Diego. |
|
|
Re: Trunk is closed for LTO mergeOn Sat, Oct 3, 2009 at 4:34 PM, Diego Novillo <dnovillo@...> wrote:
> On Sat, Oct 3, 2009 at 10:30, Toon Moene <toon@...> wrote: > >> So tomorrow I plan to svn up my gcc trunk, recompile it for C and Fortran, >> recompile our Weather Forecasting system with it, and see what happens (the >> compile of the Weather code doesn't use -flto yet, obviously. > > Thanks, that would be great. Please file bugs you find with > 'Component: lto' and 'Reported against: lto'. Actually after the merge it would be 'Reported against: 4.5.0'. I plan to move all bugs to that version after the merge (I guess we'll retire the branch then). Richard. |
|
|
Re: Trunk is closed for LTO mergeOn Sat, Oct 3, 2009 at 10:44, Richard Guenther
<richard.guenther@...> wrote: > On Sat, Oct 3, 2009 at 4:34 PM, Diego Novillo <dnovillo@...> wrote: >> >> Thanks, that would be great. Please file bugs you find with >> 'Component: lto' and 'Reported against: lto'. > > Actually after the merge it would be 'Reported against: 4.5.0'. I plan to move > all bugs to that version after the merge (I guess we'll retire the branch then). Ah, good point. Yes, I will close the branch after the merge. Diego. |
|
|
Re: Trunk is closed for LTO mergeI wrote:
> [T]omorrow I plan to svn up my gcc trunk, recompile it for C and > Fortran, recompile our Weather Forecasting system with it, and see what > happens (the compile of the Weather code doesn't use -flto yet, obviously. I did so, svn up'd to revision 152437. The build (with --with-libelf=/usr/local pointing to my private installation of libelf 0.8.12 in preference of Debian Testing's libelf 0.8.10) successfully compiled all of HIRLAM (see http://hirlam.org). The forecast that's now running behaves normally, so compiling this code without -flto certainly works. PR 41566 (which is probably related to PR 41521, as noted by Richard Guenther) points at some code of ours that doesn't yet compile with -flto. Kind regards, and thanks to all involved with this effort ! -- Toon Moene - e-mail: toon@... - phone: +31 346 214290 Saturnushof 14, 3738 XG Maartensdijk, The Netherlands At home: http://moene.org/~toon/ Progress of GNU Fortran: http://gcc.gnu.org/gcc-4.5/changes.html |
| Free embeddable forum powered by Nabble | Forum Help |