public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/99808] [8/9/10/11 Regression] ICE in as_a, at machmode.h:365
Date: Mon, 29 Mar 2021 07:48:18 +0000 [thread overview]
Message-ID: <bug-99808-4-F2lPMiQ3gD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99808-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99808
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2021-03-29
Target Milestone|--- |8.5
Keywords| |wrong-code
Component|debug |target
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
Priority|P3 |P2
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed. We're having a
(note 32 30 31 (var_location arg2 (const_vector:V2DF [
(const_double:DF 0.0 [0x0.0p+0])
(const_int 0 [0])
])) NOTE_INSN_VAR_LOCATION)
note which obviously will fail a scalar_float_mode assessment. This first
appears in CSE1 as
(insn 8 7 9 2 (set (reg/v:V2DF 92 [ arg2 ])
(const_vector:V2DF [
(const_double:DF 0.0 [0x0.0p+0])
(const_int 0 [0])
])) "t.c":9:22 1167 {*aarch64_simd_movv2df}
(expr_list:REG_DEAD (reg:DF 94)
(nil)))
and is likely a backend pattern issue.
next prev parent reply other threads:[~2021-03-29 7:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 6:58 [Bug debug/99808] New: " asolokha at gmx dot com
2021-03-29 7:48 ` rguenth at gcc dot gnu.org [this message]
2021-03-29 9:02 ` [Bug target/99808] " jakub at gcc dot gnu.org
2021-03-29 9:03 ` jakub at gcc dot gnu.org
2021-03-29 9:14 ` jakub at gcc dot gnu.org
2021-03-29 10:16 ` jakub at gcc dot gnu.org
2021-03-29 10:21 ` ktkachov at gcc dot gnu.org
2021-03-29 10:55 ` cvs-commit at gcc dot gnu.org
2021-03-30 13:08 ` cvs-commit at gcc dot gnu.org
2021-03-31 9:39 ` cvs-commit at gcc dot gnu.org
2021-03-31 9:39 ` cvs-commit at gcc dot gnu.org
2021-05-07 10:36 ` cvs-commit at gcc dot gnu.org
2021-05-07 10:38 ` cvs-commit at gcc dot gnu.org
2021-05-07 14:14 ` cvs-commit at gcc dot gnu.org
2021-05-07 14:16 ` cvs-commit 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-99808-4-F2lPMiQ3gD@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).