Re: [committed] Fix more problems with new linker warnings

2022-09-01 Thread Martin Liška
On 8/31/22 17:49, Jeff Law wrote: > > > On 8/22/2022 3:39 AM, Martin Liška wrote: >> On 4/28/22 18:10, Jeff Law via Gcc-patches wrote: >>> As I mentioned in the original thread, my change to pr94157_0 was an >>> attempt to avoid these warnings by passing a magic flag to the linker.  Of >>> cour

Re: [committed] Fix more problems with new linker warnings

2022-08-31 Thread Jeff Law via Gcc-patches
On 8/22/2022 3:39 AM, Martin Liška wrote: On 4/28/22 18:10, Jeff Law via Gcc-patches wrote: As I mentioned in the original thread, my change to pr94157_0 was an attempt to avoid these warnings by passing a magic flag to the linker.  Of course we may not be using GNU ld.  Or we may be on a n

Re: [committed] Fix more problems with new linker warnings

2022-08-22 Thread Martin Liška
On 4/28/22 18:10, Jeff Law via Gcc-patches wrote: > As I mentioned in the original thread, my change to pr94157_0 was an attempt > to avoid these warnings by passing a magic flag to the linker.  Of course we > may not be using GNU ld.  Or we may be on a non-elf target where the flag I > used doe

Re: [committed] Fix more problems with new linker warnings

2022-05-10 Thread H.J. Lu via Gcc-patches
On Thu, Apr 28, 2022 at 11:52 PM Richard Biener wrote: > > On Thu, Apr 28, 2022 at 7:54 PM H.J. Lu wrote: > > > > On Thu, Apr 28, 2022 at 9:59 AM Jeff Law wrote: > > > > > > > > > > > > On 4/28/2022 10:27 AM, H.J. Lu wrote: > > > > On Thu, Apr 28, 2022 at 9:10 AM Jeff Law via Gcc-patches > > > >

Re: [committed] Fix more problems with new linker warnings

2022-04-28 Thread Richard Biener via Gcc-patches
On Thu, Apr 28, 2022 at 7:54 PM H.J. Lu wrote: > > On Thu, Apr 28, 2022 at 9:59 AM Jeff Law wrote: > > > > > > > > On 4/28/2022 10:27 AM, H.J. Lu wrote: > > > On Thu, Apr 28, 2022 at 9:10 AM Jeff Law via Gcc-patches > > > wrote: > > >> As I mentioned in the original thread, my change to pr94157_

Re: [committed] Fix more problems with new linker warnings

2022-04-28 Thread H.J. Lu via Gcc-patches
On Thu, Apr 28, 2022 at 9:59 AM Jeff Law wrote: > > > > On 4/28/2022 10:27 AM, H.J. Lu wrote: > > On Thu, Apr 28, 2022 at 9:10 AM Jeff Law via Gcc-patches > > wrote: > >> As I mentioned in the original thread, my change to pr94157_0 was an > >> attempt to avoid these warnings by passing a magic f

Re: [committed] Fix more problems with new linker warnings

2022-04-28 Thread Jeff Law via Gcc-patches
On 4/28/2022 10:27 AM, H.J. Lu wrote: On Thu, Apr 28, 2022 at 9:10 AM Jeff Law via Gcc-patches wrote: As I mentioned in the original thread, my change to pr94157_0 was an attempt to avoid these warnings by passing a magic flag to the linker. Of course we may not be using GNU ld. Or we may b

Re: [committed] Fix more problems with new linker warnings

2022-04-28 Thread H.J. Lu via Gcc-patches
On Thu, Apr 28, 2022 at 9:10 AM Jeff Law via Gcc-patches wrote: > > As I mentioned in the original thread, my change to pr94157_0 was an > attempt to avoid these warnings by passing a magic flag to the linker. > Of course we may not be using GNU ld. Or we may be on a non-elf target > where the fl

[committed] Fix more problems with new linker warnings

2022-04-28 Thread Jeff Law via Gcc-patches
ur pruning facilities. I'll be pushing this to the trunk and gcc-12 branch. Jeffcommit af71f96631920f32ed9ec6c1c35d140dbe9992d1 Author: Jeff Law Date: Thu Apr 28 12:03:52 2022 -0400 [committed] Fix more problems with new linker warnings gcc/testsuite * gcc.dg/