public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/90620] Microblaze: ICE similar to bug 16267
Date: Mon, 31 Oct 2022 21:12:33 +0000 [thread overview]
Message-ID: <bug-90620-4-1Ax9R2Uwej@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-90620-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90620
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2022-10-31
Keywords| |ra
Status|UNCONFIRMED |WAITING
Ever confirmed|0 |1
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
[(match_operand:SI 0 "register_operand" "=&d") ;; bool output
(match_operand:SI 1 "register_operand" "=&d") ;; val output
(match_operand:SI 2 "nonimmediate_operand" "+Q") ;; memory
(match_operand:SI 3 "register_operand" "d") ;; expected value
(match_operand:SI 4 "register_operand" "d") ;; desired value
(match_operand:SI 5 "const_int_operand" "") ;; is_weak
(match_operand:SI 6 "const_int_operand" "") ;; mod_s
(match_operand:SI 7 "const_int_operand" "") ;; mod_f
(clobber (match_scratch:SI 8 "=&d"))]
"d" is:
(define_register_constraint "d" "GR_REGS"
"A general register.")
So this should work. someone will have to debug this further to see why it is
not.
Can someone please test a newer compiler and if it still happens attach the
preprocessed source?
next prev parent reply other threads:[~2022-10-31 21:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-90620-4@http.gcc.gnu.org/bugzilla/>
2022-10-31 21:08 ` pinskia at gcc dot gnu.org
2022-10-31 21:12 ` pinskia at gcc dot gnu.org [this message]
2024-04-13 1:01 ` pinskia at gcc dot gnu.org
2024-04-13 7:39 ` giulio.benetti at benettiengineering 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-90620-4-1Ax9R2Uwej@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).