public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kkojima at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/66358] [5/6 Regression] [SH] ICE: in extract_constrain_insn, at recog.c:2232
Date: Wed, 03 Jun 2015 23:27:00 -0000	[thread overview]
Message-ID: <bug-66358-4-FlxrxxztV1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66358-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66358

--- Comment #10 from Kazumoto Kojima <kkojima at gcc dot gnu.org> ---
(In reply to Oleg Endo from comment #8)
> Ah, right.  If it fixes the problem, then I think it's the only option we
> have for the release branch.

It can be used as a last resort.  It depends on whether various rtl
passes take care of hard registers or not.
I'd like to wait your pre-allocating pass.  It's surely cleaner than
that a bit unreliable artifact in prepare_move_operands.  Perhaps
both can be almost equaly invasive to the release branch.  If the pass
is enough simple and can give good results, it may be a safer bet,
especially when we are in transition to LRA.


  parent reply	other threads:[~2015-06-03 23:27 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-01  7:41 [Bug target/66358] New: " kkojima at gcc dot gnu.org
2015-06-01  7:46 ` [Bug target/66358] " kkojima at gcc dot gnu.org
2015-06-01 12:50 ` olegendo at gcc dot gnu.org
2015-06-01 13:24 ` kkojima at gcc dot gnu.org
2015-06-01 14:01 ` rguenth at gcc dot gnu.org
2015-06-01 18:35 ` olegendo at gcc dot gnu.org
2015-06-01 22:44 ` kkojima at gcc dot gnu.org
2015-06-02 21:00 ` olegendo at gcc dot gnu.org
2015-06-02 23:55 ` kkojima at gcc dot gnu.org
2015-06-03  9:04 ` olegendo at gcc dot gnu.org
2015-06-03 11:29 ` olegendo at gcc dot gnu.org
2015-06-03 23:27 ` kkojima at gcc dot gnu.org [this message]
2015-06-15 11:48 ` glaubitz at physik dot fu-berlin.de
2015-06-18  4:21 ` olegendo at gcc dot gnu.org
2015-06-22 12:07 ` rguenth at gcc dot gnu.org
2015-07-16  9:25 ` rguenth at gcc dot gnu.org
2015-08-11  7:39 ` dcb314 at hotmail dot com
2015-08-11  7:42 ` dcb314 at hotmail dot com
2021-05-14  9:47 ` [Bug target/66358] [9/10/11/12 " jakub at gcc dot gnu.org
2021-06-01  8:06 ` rguenth at gcc dot gnu.org
2022-05-27  9:35 ` [Bug target/66358] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:31 ` jakub at gcc dot gnu.org
2023-07-07 10:30 ` [Bug target/66358] [11/12/13/14 " rguenth 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-66358-4-FlxrxxztV1@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).