public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/61360] [5 Regression] ICE: in lra_update_insn_recog_data, at lra.c:1363 with -mtune=bdver4
Date: Thu, 18 Sep 2014 15:41:00 -0000	[thread overview]
Message-ID: <bug-61360-4-13KA5PYcOM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61360-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #14 from Vladimir Makarov <vmakarov at gcc dot gnu.org> ---
LRA reuses data about enabled alternatives (through code in recog.c) from
previous passes.  And the data are not right anymore.  There are two ways of
fixing that:

o enable the alternative with only "m" for LRA (remove lra_in_progress from the
definition of the attribute) as LRA can handle only "m" although reload can't.

o prevent reusing the data

I'll prepare and submit the patch for the second solution.  Although it would
be wise with perfomance point of view to implement the first one too but I
handle over this joba and the decision to x86 maintainers.


  parent reply	other threads:[~2014-09-18 15:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-29 18:14 [Bug target/61360] New: [4.10 " zsojka at seznam dot cz
2014-06-02  7:59 ` [Bug target/61360] " rguenth at gcc dot gnu.org
2014-06-13 10:25 ` trippels at gcc dot gnu.org
2014-06-13 17:15 ` trippels at gcc dot gnu.org
2014-06-14 10:27 ` rsandifo at gcc dot gnu.org
2014-06-26 10:45 ` Ganesh.Gopalasubramanian at amd dot com
2014-06-26 17:04 ` zsojka at seznam dot cz
2014-07-07 13:23 ` rguenth at gcc dot gnu.org
2014-07-10 14:24 ` trippels at gcc dot gnu.org
2014-07-17  6:32 ` trippels at gcc dot gnu.org
2014-08-20  7:47 ` [Bug target/61360] [5 " dcb314 at hotmail dot com
2014-08-26  6:48 ` Ganesh.Gopalasubramanian at amd dot com
2014-08-26  7:25 ` trippels at gcc dot gnu.org
2014-09-06 12:22 ` trippels at gcc dot gnu.org
2014-09-15 17:22 ` ubizjak at gmail dot com
2014-09-18 15:41 ` vmakarov at gcc dot gnu.org [this message]
2014-09-18 15:57 ` vmakarov at gcc dot gnu.org
2014-12-15 17:48 ` jakub at gcc dot gnu.org
2014-12-15 18:49 ` ubizjak at gmail 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-61360-4-13KA5PYcOM@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).