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/112872] [14 Regression] RISCV ICE: in store_integral_bit_field, at expmed.cc:1049 with -03 rv64gcv_zvl1024b --param=riscv-autovec-preference=fixed-vlmax
Date: Tue, 05 Dec 2023 22:10:13 +0000 [thread overview]
Message-ID: <bug-112872-4-CsQ9gsZp2g@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112872-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112872
Patrick O'Neill <patrick at rivosinc dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[14 Regression] RISCV ICE: |[14 Regression] RISCV ICE:
|in |in
|store_integral_bit_field, |store_integral_bit_field,
|at expmed.cc:1049 with -03 |at expmed.cc:1049 with -03
|rv64gcv_zvl1024b |rv64gcv_zvl1024b
| |--param=riscv-autovec-prefe
| |rence=fixed-vlmax
--- Comment #1 from Patrick O'Neill <patrick at rivosinc dot com> ---
Whoops, looks like the command got cut off when copy-pasting. Here's the full
thing:
> /scratch/tc-testing/tc-dec-4-trunk/build-rv64gcv/bin/riscv64-unknown-linux-gnu-gcc -march=rv64gcv_zvl1024b -mabi=lp64d --param=riscv-autovec-preference=fixed-vlmax -O3 red.c
next prev parent reply other threads:[~2023-12-05 22:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 22:07 [Bug target/112872] New: [14 Regression] RISCV ICE: in store_integral_bit_field, at expmed.cc:1049 with -03 rv64gcv_zvl1024b patrick at rivosinc dot com
2023-12-05 22:10 ` patrick at rivosinc dot com [this message]
2023-12-06 8:00 ` [Bug middle-end/112872] [14 Regression] RISCV ICE: in store_integral_bit_field, at expmed.cc:1049 with -03 rv64gcv_zvl1024b --param=riscv-autovec-preference=fixed-vlmax rguenth at gcc dot gnu.org
2023-12-06 8:53 ` rdapp at gcc dot gnu.org
2023-12-06 10:16 ` cvs-commit at gcc dot gnu.org
2023-12-06 18:56 ` 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-112872-4-CsQ9gsZp2g@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).