public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "patrick at rivosinc dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/111941] New: RISC-V ICE: in merge, at config/riscv/riscv-vsetvl.cc:1996
Date: Mon, 23 Oct 2023 17:45:04 +0000 [thread overview]
Message-ID: <bug-111941-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111941
Bug ID: 111941
Summary: RISC-V ICE: in merge, at
config/riscv/riscv-vsetvl.cc:1996
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: patrick at rivosinc dot com
Target Milestone: ---
Created attachment 56180
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56180&action=edit
-freport-bug output
First bad commit: r14-4773-g29331e72d0c
Confirmed to still be present on trunk: r14-4809-g55731b59e60
Building newlib 4.1.0 fails on ldtoa.c
https://sourceware.org/git/?p=newlib-cygwin.git;a=blob;f=newlib/libc/stdlib/ldtoa.c;h=1cc97151afb693b04c864243a4466038b06ac94f;hb=415fdd4279b85eeec9d54775ce13c5c412451e08
creduce'd testcase:
./bin/riscv64-unknown-elf-gcc -fno-builtin -O2 -march=rv64gv_zbb -mabi=lp64d -S
-o test.S red.c
./bin/riscv64-unknown-elf-gcc -fno-builtin -O2 -march=rv32gv_zbb -mabi=ilp32d
-S -o test.S red.c
> cat red.c
typedef struct {
short a[0]
} b;
c;
d[];
b e;
*f;
j() {
short *g = d;
int h;
unsigned short i;
for (; h < 10; h++)
i |= *f++;
if (i)
i = 1;
h = 0;
for (; h < 10; h++)
g[h] = e.a[h];
c = i;
}
next reply other threads:[~2023-10-23 17:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 17:45 patrick at rivosinc dot com [this message]
2023-10-23 22:31 ` [Bug target/111941] " patrick at rivosinc dot com
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-111941-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).