public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/109176] [13 Regression] internal compiler error: in to_constant, at poly-int.h:504
Date: Wed, 22 Mar 2023 08:47:48 +0000 [thread overview]
Message-ID: <bug-109176-4-1jHwVbtydz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109176-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109176
--- Comment #13 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Unfortunately the patch breaks quite a lot of tests on x86_64:
+FAIL: c-c++-common/goacc/firstprivate-mappings-1.c (internal compiler error:
in gimple_expand_vec_cond_expr, at gimple-isel.cc:249)
+FAIL: gcc.target/i386/sse2-pr88547-1.c (internal compiler error: in
gimple_expand_vec_cond_expr, at gimple-isel.cc:281)
+FAIL: gcc.target/i386/sse2-pr88547-2.c (internal compiler error: in
gimple_expand_vec_cond_expr, at gimple-isel.cc:281)
+FAIL: gcc.target/i386/sse4_1-pr88547-1.c (internal compiler error: in
gimple_expand_vec_cond_expr, at gimple-isel.cc:281)
+FAIL: gcc.target/i386/sse4_1-pr88547-2.c (internal compiler error: in
gimple_expand_vec_cond_expr, at gimple-isel.cc:281)
+FAIL: gdc.dg/torture/simd_blendvector.d -O0 (internal compiler error: in
gimple_expand_vec_cond_expr, at gimple-isel.cc:281)
+FAIL: gdc.dg/torture/simd_blendvector.d -O0 -g (internal compiler error: in
gimple_expand_vec_cond_expr, at gimple-isel.cc:281)
+FAIL: g++.dg/tree-ssa/pr88152-1.C (internal compiler error: in
gimple_expand_vec_cond_expr, at gimple-isel.cc:281)
+FAIL: c-c++-common/goacc/firstprivate-mappings-1.c -std=c++11 (internal
compiler error: in gimple_expand_vec_cond_expr, at gimple-isel.cc:249)
+FAIL: c-c++-common/goacc/firstprivate-mappings-1.c -std=c++14 (internal
compiler error: in gimple_expand_vec_cond_expr, at gimple-isel.cc:249)
+FAIL: c-c++-common/goacc/firstprivate-mappings-1.c -std=c++17 (internal
compiler error: in gimple_expand_vec_cond_expr, at gimple-isel.cc:249)
+FAIL: c-c++-common/goacc/firstprivate-mappings-1.c -std=c++20 (internal
compiler error: in gimple_expand_vec_cond_expr, at gimple-isel.cc:249)
+FAIL: c-c++-common/goacc/firstprivate-mappings-1.c -std=c++2b (internal
compiler error: in gimple_expand_vec_cond_expr, at gimple-isel.cc:249)
+FAIL: c-c++-common/goacc/firstprivate-mappings-1.c -std=c++98 (internal
compiler error: in gimple_expand_vec_cond_expr, at gimple-isel.cc:249)
+FAIL: g++.dg/goacc/firstprivate-mappings-1.C -std=c++11 (internal compiler
error: in gimple_expand_vec_cond_expr, at gimple-isel.cc:249)
+FAIL: g++.dg/goacc/firstprivate-mappings-1.C -std=c++14 (internal compiler
error: in gimple_expand_vec_cond_expr, at gimple-isel.cc:249)
+FAIL: g++.dg/goacc/firstprivate-mappings-1.C -std=c++17 (internal compiler
error: in gimple_expand_vec_cond_expr, at gimple-isel.cc:249)
+FAIL: g++.dg/goacc/firstprivate-mappings-1.C -std=c++20 (internal compiler
error: in gimple_expand_vec_cond_expr, at gimple-isel.cc:249)
+FAIL: g++.dg/goacc/firstprivate-mappings-1.C -std=c++2b (internal compiler
error: in gimple_expand_vec_cond_expr, at gimple-isel.cc:249)
+FAIL: g++.dg/goacc/firstprivate-mappings-1.C -std=c++98 (internal compiler
error: in gimple_expand_vec_cond_expr, at gimple-isel.cc:249)
+FAIL: libgomp.oacc-c/../libgomp.oacc-c-c++-common/firstprivate-mappings-1.c
-DACC_DEVICE_TYPE_host=1 -DACC_MEM_SHARED=1 -foffload=disable -O2 (internal
compiler error: in gimple_expand_vec_cond_expr, at gimple-isel.cc:249)
+FAIL: libgomp.oacc-c++/../libgomp.oacc-c-c++-common/firstprivate-mappings-1.c
-DACC_DEVICE_TYPE_host=1 -DACC_MEM_SHARED=1 -foffload=disable -O2 (internal
compiler error: in gimple_expand_vec_cond_expr, at gimple-isel.cc:249)
+FAIL: libgomp.oacc-c++/firstprivate-mappings-1.C -DACC_DEVICE_TYPE_host=1
-DACC_MEM_SHARED=1 -foffload=disable -O2 (internal compiler error: in
gimple_expand_vec_cond_expr, at gimple-isel.cc:249)
next prev parent reply other threads:[~2023-03-22 8:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 16:19 [Bug c++/109176] New: " malat at debian dot org
2023-03-17 16:43 ` [Bug c++/109176] " malat at debian dot org
2023-03-17 17:54 ` [Bug tree-optimization/109176] " ktkachov at gcc dot gnu.org
2023-03-20 9:17 ` [Bug tree-optimization/109176] [13 Regression] " rguenth at gcc dot gnu.org
2023-03-20 9:37 ` ktkachov at gcc dot gnu.org
2023-03-20 13:59 ` jakub at gcc dot gnu.org
2023-03-20 15:35 ` jakub at gcc dot gnu.org
2023-03-21 9:25 ` jakub at gcc dot gnu.org
2023-03-21 9:53 ` rguenth at gcc dot gnu.org
2023-03-21 10:28 ` jakub at gcc dot gnu.org
2023-03-21 10:41 ` jakub at gcc dot gnu.org
2023-03-21 10:57 ` ktkachov at gcc dot gnu.org
2023-03-21 12:03 ` jakub at gcc dot gnu.org
2023-03-21 12:12 ` rguenth at gcc dot gnu.org
2023-03-22 8:47 ` jakub at gcc dot gnu.org [this message]
2023-03-22 12:03 ` jakub at gcc dot gnu.org
2023-03-22 12:08 ` jakub at gcc dot gnu.org
2023-03-23 9:04 ` cvs-commit at gcc dot gnu.org
2023-03-23 9:08 ` [Bug tree-optimization/109176] [11/12 " jakub at gcc dot gnu.org
2023-04-18 7:15 ` cvs-commit at gcc dot gnu.org
2023-04-18 7:21 ` [Bug tree-optimization/109176] [11 " jakub at gcc dot gnu.org
2023-04-26 6:58 ` rguenth at gcc dot gnu.org
2023-05-02 20:16 ` cvs-commit at gcc dot gnu.org
2023-05-03 10:45 ` jakub 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-109176-4-1jHwVbtydz@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).