On Mon, 2022-02-28 at 18:47 +0100, Richard Biener wrote:
>
>
> > Am 28.02.2022 um 16:31 schrieb David Malcolm via Gcc-patches <
> > gcc-patches@gcc.gnu.org>:
> >
> > On Mon, 2022-02-28 at 12:49 +0100, Martin Liška wrote:
> > > Use flag_checking instead of CHECKING_P
> > > and run toplev::finali
> Am 28.02.2022 um 16:31 schrieb David Malcolm via Gcc-patches
> :
>
> On Mon, 2022-02-28 at 12:49 +0100, Martin Liška wrote:
>> Use flag_checking instead of CHECKING_P
>> and run toplev::finalize only if there is not error seen.
>>
>> Patch can bootstrap on x86_64-linux-gnu and survives reg
On Mon, 2022-02-28 at 12:49 +0100, Martin Liška wrote:
> Use flag_checking instead of CHECKING_P
> and run toplev::finalize only if there is not error seen.
>
> Patch can bootstrap on x86_64-linux-gnu and survives regression
> tests.
Did the testing include the libgccjit test suite? ("jit" is no
On Mon, Feb 28, 2022 at 12:49 PM Martin Liška wrote:
>
> Use flag_checking instead of CHECKING_P
> and run toplev::finalize only if there is not error seen.
>
> Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
>
> Ready to be installed?
OK.
Richard.
> Thanks,
> Martin
>
>
Use flag_checking instead of CHECKING_P
and run toplev::finalize only if there is not error seen.
Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
Ready to be installed?
Thanks,
Martin
PR ipa/104648
gcc/ChangeLog:
* main.cc (main): Use flag_checking inste