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 rtl-optimization/95267] [ICE][gcse]: in process_insert_insn at gcse.c
Date: Fri, 22 May 2020 04:07:15 +0000 [thread overview]
Message-ID: <bug-95267-4-plbiCztCEB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95267-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95267
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |INVALID
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
The internals documentation documents this even, read:
https://gcc.gnu.org/onlinedocs/gccint/RTL-Template.html#index-match_005fdup
>From that:
Note that match_dup should not be used to tell the compiler that a particular
register is being used for two operands (example: add that adds one register to
another; the second register is both an input operand and the output operand).
Use a matching constraint (see Simple Constraints) for those.
next prev parent reply other threads:[~2020-05-22 4:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 3:04 [Bug rtl-optimization/95267] New: " xuemaosheng at huawei dot com
2020-05-22 3:31 ` [Bug rtl-optimization/95267] " pinskia at gcc dot gnu.org
2020-05-22 3:38 ` xuemaosheng at huawei dot com
2020-05-22 4:07 ` pinskia at gcc dot gnu.org [this message]
2020-05-22 5:03 ` xuemaosheng at huawei dot com
2020-05-22 5:24 ` pinskia at gcc dot gnu.org
2020-05-22 6:12 ` zhongyunde at tom dot com
2020-05-22 6:30 ` xuemaosheng at huawei 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-95267-4-plbiCztCEB@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).