public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "acoplan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/109800] New: [11/12/13/14 Regression] arm: ICE (segfault) loading double with -mpure-code -mbig-endian
Date: Wed, 10 May 2023 16:32:59 +0000 [thread overview]
Message-ID: <bug-109800-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109800
Bug ID: 109800
Summary: [11/12/13/14 Regression] arm: ICE (segfault) loading
double with -mpure-code -mbig-endian
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: acoplan at gcc dot gnu.org
Target Milestone: ---
The following fails:
$ cat t.c
double f() { return 5.0; }
$ gcc/xgcc -B gcc -c -S -o /dev/null -O2 -march=armv7-m -mfloat-abi=hard
-mfpu=fpv4-sp-d16 -mbig-endian -mpure-code t.c
xgcc: internal compiler error: Segmentation fault signal terminated program cc1
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
See <https://gcc.gnu.org/bugs/> for instructions.
It started with r11-966-g9a182ef9ee011935d827ab5c6c9a7cd8e22257d8 .
Looking at the dumpfile 291r.split1, it looks like we end up splitting
indefinitely:
;; Function f (f, funcdef_no=0, decl_uid=5948, cgraph_uid=1, symbol_order=0)
Splitting with gen_split_111 (vfp.md:2138)
scanning new insn with uid = 12.
scanning new insn with uid = 13.
deleting insn with uid = 9.
Splitting with gen_split_111 (vfp.md:2138)
scanning new insn with uid = 14.
scanning new insn with uid = 15.
deleting insn with uid = 12.
Splitting with gen_split_111 (vfp.md:2138)
scanning new insn with uid = 16.
scanning new insn with uid = 17.
deleting insn with uid = 14.
I think we can adjust the splitter to avoid the new simplification introduced
above from undoing our subreg punning.
next reply other threads:[~2023-05-10 16:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 16:32 acoplan at gcc dot gnu.org [this message]
2023-05-11 6:25 ` [Bug target/109800] " rguenth at gcc dot gnu.org
2023-05-11 11:21 ` acoplan at gcc dot gnu.org
2023-05-25 12:35 ` cvs-commit at gcc dot gnu.org
2023-05-29 10:08 ` jakub at gcc dot gnu.org
2023-06-07 14:12 ` cvs-commit at gcc dot gnu.org
2023-06-08 17:31 ` [Bug target/109800] [11/12 " cvs-commit at gcc dot gnu.org
2023-06-09 11:18 ` [Bug target/109800] [11 " cvs-commit at gcc dot gnu.org
2023-06-09 11:19 ` acoplan 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-109800-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: 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).