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/108603] New: [11/12 Regression] ICE in output_operand_lossage with SVE and ilp32
Date: Mon, 30 Jan 2023 18:12:53 +0000 [thread overview]
Message-ID: <bug-108603-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108603
Bug ID: 108603
Summary: [11/12 Regression] ICE in output_operand_lossage with
SVE and ilp32
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:
$ gcc/xgcc -B gcc -v
Reading specs from gcc/specs
COLLECT_GCC=gcc/xgcc
COLLECT_LTO_WRAPPER=gcc/lto-wrapper
Target: aarch64-none-elf
Configured with: /home/alecop01/toolchain/src/gcc/configure
--prefix=/data_sdb/toolchain/cc1s/aarch64 --enable-langauges=c,c++
--disable-bootstrap --target=aarch64-none-elf
Thread model: single
Supported LTO compression algorithms: zlib
gcc version 13.0.1 20230130 (experimental) (GCC)
$ cat t.c
int a[128];
long long *p;
void f() {
for (long i = 0; i < sizeof(long); i++)
p[i] = a[i];
}
$ gcc/xgcc -B gcc -c t.c -O2 -march=armv8.2-a+sve -mabi=ilp32 -fdata-sections
t.c:6:1: internal compiler error: output_operand: invalid expression as operand
6 | }
| ^
0xa99b40 output_operand_lossage(char const*, ...)
/home/alecop01/toolchain/src/gcc/gcc/final.cc:3190
0xa9a3dd output_addr_const(_IO_FILE*, rtx_def*)
/home/alecop01/toolchain/src/gcc/gcc/final.cc:3787
0xa9a163 output_addr_const(_IO_FILE*, rtx_def*)
/home/alecop01/toolchain/src/gcc/gcc/final.cc:3767
0x12c647e assemble_integer_with_op(char const*, rtx_def*)
/home/alecop01/toolchain/src/gcc/gcc/varasm.cc:2845
0x12c64d2 default_assemble_integer(rtx_def*, unsigned int, int)
/home/alecop01/toolchain/src/gcc/gcc/varasm.cc:2861
0x12c652c assemble_integer(rtx_def*, unsigned int, unsigned int, int)
/home/alecop01/toolchain/src/gcc/gcc/varasm.cc:2877
0x12c6d56 output_constant_pool_1
/home/alecop01/toolchain/src/gcc/gcc/varasm.cc:4170
0x12dc5c6 output_constant_pool_contents
/home/alecop01/toolchain/src/gcc/gcc/varasm.cc:4327
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.
next reply other threads:[~2023-01-30 18:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 18:12 acoplan at gcc dot gnu.org [this message]
2023-01-31 8:46 ` [Bug target/108603] [12/13 " rguenth at gcc dot gnu.org
2023-02-06 14:23 ` marxin at gcc dot gnu.org
2023-02-09 10:34 ` rsandifo at gcc dot gnu.org
2023-02-21 12:51 ` rguenth at gcc dot gnu.org
2023-03-02 10:30 ` cvs-commit at gcc dot gnu.org
2023-04-03 8:57 ` [Bug target/108603] [12 " cvs-commit at gcc dot gnu.org
2023-04-03 9:02 ` rsandifo 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-108603-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).