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
>
> 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
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
> 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
> >
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
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
> 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 -
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
> 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
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
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 behaviour of ld -r w/o plugin
3) read LTO files
11 matches
Mail list logo
