From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 9CB673857C48; Fri, 13 Jan 2023 13:25:45 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9CB673857C48 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1673616345; bh=31xv1XEToCrwvWrJ5oAbi1cySUJLctpKOsDTgk5NJ2U=; h=From:To:Subject:Date:In-Reply-To:References:From; b=rlD8SGrllcQp9kGU9BCH6QBQXnAl4ha4sjRUohSyHpNodHib6e3HGBOPH3tA3M3k5 V5Lu4GeaEx+RK8pv1o8g5dsKP7qsmKVbGrtM3OM8yI1zT5EP99CAnbxBnmULP9giey i7yXCu/TqmnasTQ/06NGRLcOJ3WqP5FS8WMZSogU= From: "aldyh at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/107608] [13 Regression] Failure on fold-overflow-1.c and pr95115.c Date: Fri, 13 Jan 2023 13:25:44 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 13.0 X-Bugzilla-Keywords: missed-optimization, wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: aldyh at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 13.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.isobsolete attachments.created Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D107608 Aldy Hernandez changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #54253|0 |1 is obsolete| | --- Comment #30 from Aldy Hernandez --- Created attachment 54266 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D54266&action=3Dedit proposed patch There seem to be some nonsensical (??unrelated??) regressions on a GCC test= run: > FAIL: c-c++-common/diagnostic-format-sarif-file-4.c -std=3Dgnu++14 scan= -sarif-file "text": " int \\\\u6587\\\\u5b57\\\\u5316\\\\u3051 =3D=20 > FAIL: c-c++-common/diagnostic-format-sarif-file-4.c -std=3Dgnu++17 scan= -sarif-file "text": " int \\\\u6587\\\\u5b57\\\\u5316\\\\u3051 =3D=20 > FAIL: c-c++-common/diagnostic-format-sarif-file-4.c -std=3Dgnu++20 scan= -sarif-file "text": " int \\\\u6587\\\\u5b57\\\\u5316\\\\u3051 =3D=20 > FAIL: c-c++-common/diagnostic-format-sarif-file-4.c -std=3Dgnu++98 scan= -sarif-file "text": " int \\\\u6587\\\\u5b57\\\\u5316\\\\u3051 =3D=20 > FAIL: g++.dg/pr71488.C (test for excess errors) > FAIL: g++.dg/guality/pr55665.C -O2 -flto -fno-use-linker-plugin -flto-p= artition=3Dnone line 23 p =3D=3D 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 =3D=20 < FAIL: g++.dg/pr71488.C (test for excess errors) < FAIL: g++.dg/guality/pr55665.C -O2 -flto -fno-use-linker-plugin -flto-partition=3Dnone line 23 p =3D=3D 40 > FAIL: ./index0-out.go execution, -O0 -g -fno-var-tracking-assignments=20 > FAIL: go.test/test/fixedbugs/issue27836.dir/=C3=83=E2=80=9Efoo.go -O -I.= (test for excess errors) > FAIL: go.test/test/fixedbugs/issue27836.dir/=C3=83=E2=80=9Emain.go -O -I= . (test for excess errors) The g++.dg/pr71488.C results look exactly the same when examining the g++.l= og 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/../../gc= cgo -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/./li= bgo -O -I. -w -pedantic-errors -c -o =C3=84foo.o /home/aldyh/bld/autobuilds/4081bed04fc/src/gcc/testsuite/go.test/test/fixed= bugs/issue27836.dir/=C3=84foo.go go1: fatal error: cannot open /home/aldyh/bld/autobuilds/4081bed04fc/src/gcc/testsuite/go.test/test/fixed= bugs/issue27836.dir/=C3=83foo.go: No such file or directory compilation terminated. compiler exited with status 1 FAIL: go.test/test/fixedbugs/issue27836.dir/=C3=84foo.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/fixed= bugs/issue27836.dir/=C3=83foo.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.=