public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/108603] [12/13 Regression] ICE in output_operand_lossage with SVE and ilp32
Date: Thu, 09 Feb 2023 10:34:22 +0000 [thread overview]
Message-ID: <bug-108603-4-EOIP3F9p65@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108603-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108603
rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2023-02-09
CC| |rsandifo at gcc dot gnu.org
Status|UNCONFIRMED |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |rsandifo at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #2 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
Mine.
(insn 30 29 31 4 (set (reg/f:DI 116)
(mem/u/c:DI (reg/f:DI 117) [0 S8 A64])) "...":5:13 -1
(expr_list:REG_EQUAL (const:DI (reg:DI 111))
(nil)))
Heh.
next prev parent reply other threads:[~2023-02-09 10:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 18:12 [Bug target/108603] New: [11/12 " acoplan at gcc dot gnu.org
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 [this message]
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-EOIP3F9p65@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).