https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107608
Aldy Hernandez <aldyh at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #54253|0 |1
is obsolete| |
--- Comment #30 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
Created attachment 54266
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54266&action=edit
proposed patch
There seem to be some nonsensical (??unrelated??) regressions on a GCC testrun:
> FAIL: c-c++-common/diagnostic-format-sarif-file-4.c -std=gnu++14
> scan-sarif-file "text": " int \\\\u6587\\\\u5b57\\\\u5316\\\\u3051 =
> FAIL: c-c++-common/diagnostic-format-sarif-file-4.c -std=gnu++17
> scan-sarif-file "text": " int \\\\u6587\\\\u5b57\\\\u5316\\\\u3051 =
> FAIL: c-c++-common/diagnostic-format-sarif-file-4.c -std=gnu++20
> scan-sarif-file "text": " int \\\\u6587\\\\u5b57\\\\u5316\\\\u3051 =
> FAIL: c-c++-common/diagnostic-format-sarif-file-4.c -std=gnu++98
> scan-sarif-file "text": " int \\\\u6587\\\\u5b57\\\\u5316\\\\u3051 =
> FAIL: g++.dg/pr71488.C (test for excess errors)
> FAIL: g++.dg/guality/pr55665.C -O2 -flto -fno-use-linker-plugin
> -flto-partition=none line 23 p == 40
< FAIL: gcc.dg/fold-overflow-1.c scan-assembler-times 2139095040 2
> FAIL: c-c++-common/diagnostic-format-sarif-file-4.c -Wc++-compat
> scan-sarif-file "text": " int \\\\u6587\\\\u5b57\\\\u5316\\\\u3051 =
< FAIL: g++.dg/pr71488.C (test for excess errors)
< FAIL: g++.dg/guality/pr55665.C -O2 -flto -fno-use-linker-plugin
-flto-partition=none line 23 p == 40
> FAIL: ./index0-out.go execution, -O0 -g -fno-var-tracking-assignments
> FAIL: go.test/test/fixedbugs/issue27836.dir/Äfoo.go -O -I. (test for excess
> errors)
> FAIL: go.test/test/fixedbugs/issue27836.dir/Ämain.go -O -I. (test for
> excess errors)
The g++.dg/pr71488.C results look exactly the same when examining the g++.log
file.
go always acts up for me, so I have no idea if this is legitimate:
spawn -ignore SIGHUP
/opt/notnfs/aldyh/bld/autobuilds/4081bed04fc/bld/gcc/testsuite/go3/../../gccgo
-B/opt/notnfs/aldyh/bld/autobuilds/4081bed04fc/bld/gcc/testsuite/go3/../../
-fdiagnostics-plain-output
-I/opt/notnfs/aldyh/bld/autobuilds/4081bed04fc/bld/x86_64-pc-linux-gnu/./libgo
-O -I. -w -pedantic-errors -c -o Äfoo.o
/home/aldyh/bld/autobuilds/4081bed04fc/src/gcc/testsuite/go.test/test/fixedbugs/issue27836.dir/Äfoo.go
go1: fatal error: cannot open
/home/aldyh/bld/autobuilds/4081bed04fc/src/gcc/testsuite/go.test/test/fixedbugs/issue27836.dir/Ã<U+0084>foo.go:
No such file or directory
compilation terminated.
compiler exited with status 1
FAIL: go.test/test/fixedbugs/issue27836.dir/Äfoo.go -O -I. (test for excess
errors)
Excess errors:
go1: fatal error: cannot open
/home/aldyh/bld/autobuilds/4081bed04fc/src/gcc/testsuite/go.test/test/fixedbugs/issue27836.dir/Ã<U+0084>foo.go:
No such file or directory
compilation terminated.
I think this is all testsuite noise, but I'm not sure.
As mentioned, there are no glibc regressions, only fixes.
