public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/64110] [5 Regression] ICE: Max. number of generated reload insns per insn is achieved (90)
Date: Fri, 09 Jan 2015 16:36:00 -0000 [thread overview]
Message-ID: <bug-64110-4-ba8HSuUMVF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64110-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64110
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |law at gcc dot gnu.org
--- Comment #16 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Vladimir Makarov from comment #15)
> Jakub, I've checked this particular test and LRA works in the same way as
> reload and as specified in the GCC documentation which mainly says that '!'
> is ignored only when *all* operands satisfy the alternative constraints. In
> this case there is one reload therefore alternative with '!r' is rejected.
> I understand that for this insn the desirable behaviour is to reject
> alternative only when operand with '!r' needs a reload.
>
> I could implement such functionality. The following unreserved special
> characters can be used as such modifier with the new functionality:
> @ $ ^ -
>
> What character would you prefer, Jakub?
No strong opinion, perhaps @ ? Jeff, what would you prefer?
next prev parent reply other threads:[~2015-01-09 16:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-29 4:25 [Bug c++/64110] New: " thiago at kde dot org
2014-11-29 4:41 ` [Bug c++/64110] " thiago at kde dot org
2014-11-29 7:17 ` thiago at kde dot org
2014-11-29 7:20 ` thiago at kde dot org
2014-11-29 13:02 ` [Bug c++/64110] [5 Regression] " hjl.tools at gmail dot com
2014-12-01 12:17 ` jakub at gcc dot gnu.org
2014-12-01 12:37 ` jakub at gcc dot gnu.org
2014-12-03 4:00 ` vmakarov at gcc dot gnu.org
2014-12-03 9:35 ` [Bug rtl-optimization/64110] " mpolacek at gcc dot gnu.org
2014-12-11 11:41 ` rguenth at gcc dot gnu.org
2014-12-12 20:11 ` vmakarov at gcc dot gnu.org
2014-12-17 3:31 ` hjl.tools at gmail dot com
2014-12-17 8:36 ` jakub at gcc dot gnu.org
2014-12-17 21:30 ` vmakarov at gcc dot gnu.org
2014-12-17 21:37 ` vmakarov at gcc dot gnu.org
2014-12-17 22:55 ` jakub at gcc dot gnu.org
2015-01-09 16:24 ` vmakarov at gcc dot gnu.org
2015-01-09 16:36 ` jakub at gcc dot gnu.org [this message]
2015-01-09 16:48 ` law at redhat dot com
2015-01-15 20:27 ` vmakarov at gcc dot gnu.org
2015-01-20 21:57 ` law at redhat 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-64110-4-ba8HSuUMVF@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).