public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sjames at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/114137] ICE when building lua-5.4.6 with -fharden-control-flow-redundancy on x86 (error: invalid rtl sharing found in the insn)
Date: Tue, 27 Feb 2024 19:14:08 +0000 [thread overview]
Message-ID: <bug-114137-4-HVvTSXwKZZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114137-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114137
--- Comment #4 from Sam James <sjames at gcc dot gnu.org> ---
I have another testcase where it works with -save-temps or the GC params.
bibtexu-3.71_p20210325:
```
# i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -DUNIX -DKPATHSEA
-DU_DISABLE_RENAMING=1 -I/usr/include -DUTF_8 -Wimplicit -Wreturn-type -O3
-pipe -march=i686 -fdiagnostics-color=always -mfpmath=sse -msse -msse2
-fno-vect-cost-model -fharden-control-flow-redundancy -fpermissive -c -o
bibtexu-bibtex-4.o bibtex-4.c -fharden-control-flow-redundancy
during RTL pass: rtl pre
In file included from bibtex-4.c:130:
bibtex-4.c: In function ‘x_format_name’:
sysdep.h:210:37: internal compiler error: Segmentation fault
210 | #define END }
| ^
bibtex-4.c:1303:1: note: in expansion of macro ‘END’
1303 | END
| ^~~
0x579d3dc9 crash_signal
/usr/src/debug/sys-devel/gcc-14.0.9999/gcc-14.0.9999/gcc/toplev.cc:319
0x586e7ff0 mark_used_flags
/usr/src/debug/sys-devel/gcc-14.0.9999/gcc-14.0.9999/gcc/emit-rtl.cc:3364
0x586e6638 mark_used_flags
/usr/src/debug/sys-devel/gcc-14.0.9999/gcc-14.0.9999/gcc/emit-rtl.cc:3416
0x586e6638 mark_used_flags
/usr/src/debug/sys-devel/gcc-14.0.9999/gcc-14.0.9999/gcc/emit-rtl.cc:3411
0x586e6638 mark_used_flags
/usr/src/debug/sys-devel/gcc-14.0.9999/gcc-14.0.9999/gcc/emit-rtl.cc:3411
0x586e6638 reset_used_flags(rtx_def*)
/usr/src/debug/sys-devel/gcc-14.0.9999/gcc-14.0.9999/gcc/emit-rtl.cc:3428
0x586e6638 reset_insn_used_flags
/usr/src/debug/sys-devel/gcc-14.0.9999/gcc-14.0.9999/gcc/emit-rtl.cc:3094
0x586e6638 reset_all_used_flags
/usr/src/debug/sys-devel/gcc-14.0.9999/gcc-14.0.9999/gcc/emit-rtl.cc:3111
0x586e4737 verify_rtl_sharing()
/usr/src/debug/sys-devel/gcc-14.0.9999/gcc-14.0.9999/gcc/emit-rtl.cc:3147
0x5832756c execute_function_todo
/usr/src/debug/sys-devel/gcc-14.0.9999/gcc-14.0.9999/gcc/passes.cc:2109
0x5832756c do_per_function
/usr/src/debug/sys-devel/gcc-14.0.9999/gcc-14.0.9999/gcc/passes.cc:1687
0x5832756c execute_todo
/usr/src/debug/sys-devel/gcc-14.0.9999/gcc-14.0.9999/gcc/passes.cc:2142
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
Please include the complete backtrace with any bug report.
See <https://bugs.gentoo.org/> for instructions.
```
For both test cases, -fno-harden-control-flow-redundancy also suppresses the
ICE.
next prev parent reply other threads:[~2024-02-27 19:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 17:47 [Bug rtl-optimization/114137] New: " sjames at gcc dot gnu.org
2024-02-27 17:48 ` [Bug rtl-optimization/114137] " sjames at gcc dot gnu.org
2024-02-27 18:18 ` [Bug target/114137] " sjames at gcc dot gnu.org
2024-02-27 18:20 ` sjames at gcc dot gnu.org
2024-02-27 19:14 ` sjames at gcc dot gnu.org [this message]
2024-02-27 19:16 ` sjames at gcc dot gnu.org
2024-03-08 11:01 ` aoliva 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-114137-4-HVvTSXwKZZ@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).