https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112374

--- Comment #38 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
And the #c29 change actually seems to fix all the testcases here with
-fcompare-debug -gno-statement-frontiers:
$ ~/src/gcc/obj48/gcc/xg++ -B ~/src/gcc/obj48/gcc/ -fcompare-debug
-gno-statement-frontiers pr112374-0.C -O2 -march=skylake-avx512 -S
$ ~/src/gcc/obj48/gcc/xgcc -B ~/src/gcc/obj48/gcc/ -fcompare-debug
-gno-statement-frontiers pr112374-1.c -O2 -march=skylake-avx512 -S
xgcc: error: pr112374-1.c: ‘-fcompare-debug’ failure (length)
$ ~/src/gcc/obj48/gcc/xgcc -B ~/src/gcc/obj48/gcc/ -fcompare-debug
-gno-statement-frontiers pr112374-2.c -O2 -march=skylake-avx512 -S
xgcc: error: pr112374-2.c: ‘-fcompare-debug’ failure (length)
$ ~/src/gcc/obj48/gcc/xg++ -B ~/src/gcc/obj48/gcc/ -fcompare-debug
-gno-statement-frontiers pr112374-3.C -O2 -march=skylake-avx512 -S
pr112374-3.C: In constructor ‘t::t(const long unsigned int&)’:
pr112374-3.C:4:36: warning: narrowing conversion of ‘(long unsigned int)a’ from
‘long unsigned int’ to ‘long int’ [-Wnarrowing]
    4 |   t(const unsigned long &a) : coef{a} {};
      |                                    ^
xg++: error: pr112374-3.C: ‘-fcompare-debug’ failure
$ ./xg++ -B ./ -fcompare-debug -gno-statement-frontiers pr112374-0.C -O2
-march=skylake-avx512 -S
$ ./xgcc -B ./ -fcompare-debug -gno-statement-frontiers pr112374-1.c -O2
-march=skylake-avx512 -S
$ ./xgcc -B ./ -fcompare-debug -gno-statement-frontiers pr112374-2.c -O2
-march=skylake-avx512 -S
$ ./xg++ -B ./ -fcompare-debug -gno-statement-frontiers pr112374-3.C -O2
-march=skylake-avx512 -S
pr112374-3.C: In constructor ‘t::t(const long unsigned int&)’:
pr112374-3.C:4:36: warning: narrowing conversion of ‘(long unsigned int)a’ from
‘long unsigned int’ to ‘long int’ [-Wnarrowing]
    4 |   t(const unsigned long &a) : coef{a} {};
      |                                    ^
where ~/src/gcc/obj48/gcc/ is build dir of last night's trunk and ./ is build
dir of trunk patched with #c29 patch.
pr112374-0.C is #c19, pr112374-1.c is #c21, pr112374-2.c is #c25 and
pr112374-3.C is #c30.
So, pr112374-0.C is not useful with -gno-statement-frontiers, guess I'll add
the rest into the testsuite for the patch after trying to fix the narrowing
warning in #c30.

Reply via email to