Re: Incremental LTO linking part 2: lto-plugin support

2018-06-18 Thread Sandra Loosemore
On 06/18/2018 11:37 AM, Jan Hubicka wrote: It is exactly the warning newly added by this patch. /scratch/sandra/arm-eabi-upstream/install/lib/gcc/arm-none-eabi/9.0.0/../../../../arm-none-eabi/bin/ld: warning: incremental linking of LTO and non-LTO objects; using -flinker-output=nolto-rel which

Re: Incremental LTO linking part 2: lto-plugin support

2018-06-18 Thread Jan Hubicka
> > It is exactly the warning newly added by this patch. > > /scratch/sandra/arm-eabi-upstream/install/lib/gcc/arm-none-eabi/9.0.0/../../../../arm-none-eabi/bin/ld: > warning: incremental linking of LTO and non-LTO objects; using > -flinker-output=nolto-rel which will bypass whole program optimiz

Re: Incremental LTO linking part 2: lto-plugin support

2018-06-18 Thread Sandra Loosemore
On 06/18/2018 02:45 AM, Jan Hubicka wrote: On 05/08/2018 09:14 AM, Jan Hubicka wrote: Hi, with lto, incremental linking can be meaninfuly done in three ways: 1) read LTO file and produce non-LTO .o file this is current behaviour of gcc -r or ld -r with plugin 2) read LTO files and merge

Re: Incremental LTO linking part 2: lto-plugin support

2018-06-18 Thread Jan Hubicka
> On 05/08/2018 09:14 AM, Jan Hubicka wrote: > >Hi, > >with lto, incremental linking can be meaninfuly done in three ways: > > 1) read LTO file and produce non-LTO .o file > > this is current behaviour of gcc -r or ld -r with plugin > > 2) read LTO files and merge section for later LTO > >

Re: Incremental LTO linking part 2: lto-plugin support

2018-06-17 Thread Sandra Loosemore
On 05/08/2018 09:14 AM, Jan Hubicka wrote: Hi, with lto, incremental linking can be meaninfuly done in three ways: 1) read LTO file and produce non-LTO .o file this is current behaviour of gcc -r or ld -r with plugin 2) read LTO files and merge section for later LTO this is current

Re: Incremental LTO linking part 2: lto-plugin support

2018-05-09 Thread H.J. Lu
On Wed, May 9, 2018 at 1:25 AM, Jan Hubicka wrote: >> On Tue, 8 May 2018, Jan Hubicka wrote: >> >> > > On Tue, May 8, 2018 at 8:14 AM, Jan Hubicka wrote: >> > > > Hi, >> > > > with lto, incremental linking can be meaninfuly done in three ways: >> > > > 1) read LTO file and produce non-LTO .o fil

Re: Incremental LTO linking part 2: lto-plugin support

2018-05-09 Thread Jan Hubicka
> On Tue, 8 May 2018, Jan Hubicka wrote: > > > > On Tue, May 8, 2018 at 8:14 AM, Jan Hubicka wrote: > > > > Hi, > > > > with lto, incremental linking can be meaninfuly done in three ways: > > > > 1) read LTO file and produce non-LTO .o file > > > > this is current behaviour of gcc -r or ld -

Re: Incremental LTO linking part 2: lto-plugin support

2018-05-09 Thread Richard Biener
On Tue, 8 May 2018, Jan Hubicka wrote: > > On Tue, May 8, 2018 at 8:14 AM, Jan Hubicka wrote: > > > Hi, > > > with lto, incremental linking can be meaninfuly done in three ways: > > > 1) read LTO file and produce non-LTO .o file > > > this is current behaviour of gcc -r or ld -r with plugin

Re: Incremental LTO linking part 2: lto-plugin support

2018-05-08 Thread Jan Hubicka
> On Tue, May 8, 2018 at 8:14 AM, Jan Hubicka wrote: > > Hi, > > with lto, incremental linking can be meaninfuly done in three ways: > > 1) read LTO file and produce non-LTO .o file > > this is current behaviour of gcc -r or ld -r with plugin > > 2) read LTO files and merge section for later

Re: Incremental LTO linking part 2: lto-plugin support

2018-05-08 Thread H.J. Lu
On Tue, May 8, 2018 at 8:14 AM, Jan Hubicka wrote: > Hi, > with lto, incremental linking can be meaninfuly done in three ways: > 1) read LTO file and produce non-LTO .o file > this is current behaviour of gcc -r or ld -r with plugin > 2) read LTO files and merge section for later LTO > t