public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/110313] New: [14 Regression] GCN Fiji reload ICE in 'process_alt_operands' Date: Mon, 19 Jun 2023 15:59:37 +0000 [thread overview] Message-ID: <bug-110313-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110313 Bug ID: 110313 Summary: [14 Regression] GCN Fiji reload ICE in 'process_alt_operands' Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: openmp Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: tschwinge at gcc dot gnu.org CC: ams at gcc dot gnu.org, burnus at gcc dot gnu.org, jules at gcc dot gnu.org Target Milestone: --- Target: GCN Between GCC commit 2720bbd597f56742a17119dfe80edc2ba86af255..bc6bd0d608da1609c1caeb04ab795a83720add55 (that is, 2023-05-30 - 2023-06-16) appeared some changes in GCC that cause an ICE for a small number of libgomp offloading test cases, for GCN offloading only, and with (default) '-march=fiji' only. [-PASS:-]{+FAIL: libgomp.c++/../libgomp.c-c++-common/for-9.c (internal compiler error: Segmentation fault)+} {+FAIL:+} libgomp.c++/../libgomp.c-c++-common/for-9.c (test for excess errors) [-PASS:-]{+UNRESOLVED:+} libgomp.c++/../libgomp.c-c++-common/for-9.c [-execution test-]{+compilation failed to produce executable+} [-PASS:-]{+FAIL: libgomp.c/../libgomp.c-c++-common/for-9.c (internal compiler error: Segmentation fault)+} {+FAIL:+} libgomp.c/../libgomp.c-c++-common/for-9.c (test for excess errors) [-PASS:-]{+UNRESOLVED:+} libgomp.c/../libgomp.c-c++-common/for-9.c [-execution test-]{+compilation failed to produce executable+} The latter C++ variant not always observed. Additionally (same ICE), but so far observed on one system only, when running the exact same toolchain: [-PASS:-]{+FAIL: libgomp.c/../libgomp.c-c++-common/for-16.c (internal compiler error: Segmentation fault)+} {+FAIL:+} libgomp.c/../libgomp.c-c++-common/for-16.c (test for excess errors) [-PASS:-]{+UNRESOLVED:+} libgomp.c/../libgomp.c-c++-common/for-16.c [-execution test-]{+compilation failed to produce executable+} The ICE is: spawn -ignore SIGHUP gcc ../source-gcc/libgomp/testsuite/libgomp.c/../libgomp.c-c++-common/for-9.c -I../source-gcc/libgomp/testsuite/../../include -I../source-gcc/libgomp/testsuite/.. -fmessage-length=0 -fno-diagnostics-show-caret -fdiagnostics-color=never -fopenmp -O2 -lm -o ./for-9.exe during RTL pass: reload ../source-gcc/libgomp/testsuite/libgomp.c/../libgomp.c-c++-common/for-2.h: In function 'f20_dpf_ds128_runtime': ../source-gcc/libgomp/testsuite/libgomp.c/../libgomp.c-c++-common/for-2.h:346:1: internal compiler error: Segmentation fault 0xe28adf crash_signal [...]/source-gcc/gcc/toplev.cc:314 0xc19737 process_alt_operands [...]/source-gcc/gcc/lra-constraints.cc:2789 0xc19737 curr_insn_transform [...]/source-gcc/gcc/lra-constraints.cc:4201 0xc1ed0e lra_constraints(bool) [...]/source-gcc/gcc/lra-constraints.cc:5396 0xbff652 lra(_IO_FILE*) [...]/source-gcc/gcc/lra.cc:2396 0xb9c639 do_reload [...]/source-gcc/gcc/ira.cc:5967 0xb9c639 execute [...]/source-gcc/gcc/ira.cc:6153 Please submit a full bug report, with preprocessed source (by using -freport-bug). Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions. gcn mkoffload: fatal error: x86_64-pc-linux-gnu-accel-amdgcn-amdhsa-gcc returned 1 exit status compilation terminated. lto-wrapper: fatal error: [...]/amdgcn-amdhsa/mkoffload returned 1 exit status 'gcc/lra-constraints.cc': 2778 if (operand_reg[nop] != NULL_RTX 2779 /* Output operands and matched input operands are 2780 not inherited. The following conditions do not 2781 exactly describe the previous statement but they 2782 are pretty close. */ 2783 && curr_static_id->operand[nop].type != OP_OUT 2784 && (this_alternative_matches < 0 2785 || curr_static_id->operand[nop].type != OP_IN)) 2786 { 2787 int last_reload = (lra_reg_info[ORIGINAL_REGNO 2788 (operand_reg[nop])] 2789 .last_reload); Tobias mentioned that 'operand_reg[nop]' is '(reg/f:DI 16 s16 [3483])'. It was "obvious" to try, but reverting Vlad's three recent commits: - commit r14-1891-g154c69039571c66b3a6d16ecfa9e6ff22942f59f "RA: Ignore conflicts for some pseudos from insns throwing a final exception" - commit r14-1610-g8cc8707446b77f9413654b31704f5a639673c916 "RA: Constrain class of pic offset table pseudo to general regs" - commit r14-1417-g30038a207c10a2783fa2695b62c7c8458ef05e73 "LRA: Update insn sp offset if its input reload changes SP" ... does *not* cure this issue. I've not yet tested with a non-offloading, GCN target toolchain (... with (default) '-march=fiji'). I'm now bisecting. Once we've located the "offender", I'll see about providing a reproducer -- if necessary.
next reply other threads:[~2023-06-19 15:59 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-19 15:59 tschwinge at gcc dot gnu.org [this message] 2023-06-20 8:11 ` [Bug target/110313] " rguenth at gcc dot gnu.org 2023-06-20 9:13 ` ams at gcc dot gnu.org 2023-06-20 9:21 ` tschwinge at gcc dot gnu.org 2023-06-20 9:41 ` ams at gcc dot gnu.org 2023-06-20 15:36 ` tschwinge at gcc dot gnu.org 2023-06-20 15:56 ` ams at gcc dot gnu.org 2023-06-20 20:57 ` burnus at gcc dot gnu.org 2023-06-20 21:48 ` burnus at gcc dot gnu.org 2023-06-20 22:55 ` burnus at gcc dot gnu.org 2023-06-21 6:49 ` manolis.tsamis at vrull dot eu 2023-06-21 7:25 ` tschwinge at gcc dot gnu.org 2023-06-21 8:45 ` burnus at gcc dot gnu.org 2023-06-28 14:06 ` cvs-commit 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-110313-4@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: linkBe 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).