Re: [PATCH] driver, toplevel: Avoid emitting the version information twice.

2023-02-02 Thread Richard Biener via Gcc-patches
On Thu, Feb 2, 2023 at 12:41 PM Iain Sandoe wrote: > > > > > On 30 Jan 2023, at 07:48, Richard Biener wrote: > > > > On Sun, Jan 29, 2023 at 12:35 PM Iain Sandoe via Gcc-patches > > wrote: > >> > >> Technically, this is seems to be a regression somewhere between 4.2 and > >> 4.6 but, it seems, n

Re: [PATCH] driver, toplevel: Avoid emitting the version information twice.

2023-02-02 Thread Iain Sandoe
> On 30 Jan 2023, at 07:48, Richard Biener wrote: > > On Sun, Jan 29, 2023 at 12:35 PM Iain Sandoe via Gcc-patches > wrote: >> >> Technically, this is seems to be a regression somewhere between 4.2 and >> 4.6 but, it seems, not enough for anyone to care too much. Tested on >> various Darwin

Re: [PATCH] driver, toplevel: Avoid emitting the version information twice.

2023-01-29 Thread Richard Biener via Gcc-patches
On Sun, Jan 29, 2023 at 12:35 PM Iain Sandoe via Gcc-patches wrote: > > Technically, this is seems to be a regression somewhere between 4.2 and > 4.6 but, it seems, not enough for anyone to care too much. Tested on > various Darwin versions and x86_64, powerpc64 linux, > OK for trunk {now,stage1}

[PATCH] driver, toplevel: Avoid emitting the version information twice.

2023-01-29 Thread Iain Sandoe via Gcc-patches
Technically, this is seems to be a regression somewhere between 4.2 and 4.6 but, it seems, not enough for anyone to care too much. Tested on various Darwin versions and x86_64, powerpc64 linux, OK for trunk {now,stage1}? thanks, Iain --- 8< --- For a regular compile job, with -v we emit the GCC