public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/106075] Wrong DSE with -fnon-call-exceptions
Date: Wed, 03 May 2023 12:56:50 +0000 [thread overview]
Message-ID: <bug-106075-4-1iXPnRelh7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106075-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106075
--- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> ---
Created attachment 54979
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54979&action=edit
patch
This patch fixes the testcase but it causes Ada and Go failures. I've
isolated the Ada FAILs to the dse.cc change but then I'm not really into
this RTL optimization pass nor the pecularities of Ada (or Go).
=== acats tests ===
FAIL: c37009a
FAIL: c37208a
FAIL: c41103a
FAIL: c41103b
FAIL: c41301a
FAIL: c55c02b
FAIL: c87b40a
FAIL: cc1018a
=== gnat tests ===
Running target unix/
FAIL: gnat.dg/opt47.adb execution test
=== go tests ===
Running target unix/
FAIL: go.go-torture/execute/names-1.go execution, -O1
FAIL: go.go-torture/execute/names-1.go execution, -O2
FAIL: go.go-torture/execute/names-1.go execution, -O2 -fbounds-check
FAIL: go.go-torture/execute/names-1.go execution, -O2 -fomit-frame-pointer
-finline-functions
FAIL: go.go-torture/execute/names-1.go execution, -O2 -fomit-frame-pointer
-finline-functions -funroll-loops
FAIL: go.go-torture/execute/names-1.go execution, -O3 -g
FAIL: ./index0-out.go execution, -O0 -g -fno-var-tracking-assignments
FAIL: go.test/test/235.go execution, -O2 -g
FAIL: go.test/test/chan/sieve1.go execution, -O2 -g
FAIL: go.test/test/chan/sieve2.go execution, -O2 -g
FAIL: go.test/test/cmp.go execution, -O2 -g
FAIL: go.test/test/complit.go execution, -O2 -g
FAIL: go.test/test/ddd.go execution, -O2 -g
FAIL: go.test/test/fixedbugs/bug187.go execution, -O2 -g
FAIL: go.test/test/fixedbugs/bug204.go execution, -O2 -g
FAIL: go.test/test/fixedbugs/bug447.go execution
FAIL: go.test/test/fixedbugs/bug465.dir/b.go execution, -O2 -g
FAIL: go.test/test/fixedbugs/bug483.go execution, -O2 -g
FAIL: go.test/test/fixedbugs/issue10925.go execution, -O2 -g
FAIL: go.test/test/fixedbugs/issue14553.go execution, -O2 -g
FAIL: go.test/test/fixedbugs/issue15528.go execution, -O2 -g
FAIL: go.test/test/fixedbugs/issue16095.go execution, -O2 -g
FAIL: go.test/test/fixedbugs/issue19113.go execution, -O2 -g
FAIL: go.test/test/fixedbugs/issue22881.go execution, -O2 -g
FAIL: go.test/test/fixedbugs/issue27836.dir/Ã~Dfoo.go -O -I. (test for excess
errors)
FAIL: go.test/test/fixedbugs/issue27836.dir/Ã~Dmain.go -O -I. (test for excess
errors)
FAIL: go.test/test/fixedbugs/issue39505b.go execution, -O2 -g
FAIL: go.test/test/fixedbugs/issue4909b.go execution
FAIL: go.test/test/fixedbugs/issue5162.go execution
FAIL: go.test/test/fixedbugs/issue9604b.go execution
FAIL: go.test/test/ken/range.go execution, -O2 -g
FAIL: go.test/test/slice3.go execution
FAIL: go.test/test/stringrange.go execution, -O2 -g
FAIL: go.test/test/utf.go execution, -O2 -g
(also gotools and libgo fails)
next prev parent reply other threads:[~2023-05-03 12:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 9:34 [Bug middle-end/106075] New: " hubicka at gcc dot gnu.org
2022-06-24 9:36 ` [Bug middle-end/106075] " pinskia at gcc dot gnu.org
2022-06-24 9:39 ` pinskia at gcc dot gnu.org
2022-06-24 10:39 ` rguenth at gcc dot gnu.org
2022-06-24 11:14 ` hubicka at gcc dot gnu.org
2022-06-24 11:15 ` hubicka at gcc dot gnu.org
2023-01-16 20:58 ` hubicka at gcc dot gnu.org
2023-01-17 9:16 ` rguenth at gcc dot gnu.org
2023-05-03 12:56 ` rguenth at gcc dot gnu.org [this message]
2023-05-03 12:57 ` rguenth at gcc dot gnu.org
2023-05-08 9:35 ` ebotcazou at gcc dot gnu.org
2023-05-08 13:25 ` ebotcazou at gcc dot gnu.org
2023-05-08 13:49 ` rguenther at suse dot de
2023-05-08 13:54 ` rguenth at gcc dot gnu.org
2023-05-08 13:55 ` ebotcazou at gcc dot gnu.org
2023-05-08 13:57 ` ebotcazou at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-106075-4-1iXPnRelh7@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).