public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Steven Bosscher <stevenb.gcc@gmail.com>
To: Vladimir Makarov <vmakarov@redhat.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, Jakub Jelinek <jakub@redhat.com>
Subject: Re: [patch] PR inline-asm/55934
Date: Tue, 22 Jan 2013 09:42:00 -0000	[thread overview]
Message-ID: <CABu31nP41G7Ck5qejfad2EjQd8FgYL_SZf2YZ3guahK=WBOLWg@mail.gmail.com> (raw)
In-Reply-To: <50FD6B5D.7040008@redhat.com>

On Mon, Jan 21, 2013 at 5:22 PM, Vladimir Makarov wrote:
> I'd prefer the above change than just keeping
> lra_invalidate_insn_data call.  I think it is more safe solution for other
> parts of LRA code.

I agree, but unfortunately the compiler does not...

With that lra.c change, I get extra fails:

+FAIL: gcc.target/i386/20011029-2.c (internal compiler error)
+FAIL: gcc.target/i386/20011029-2.c (test for excess errors)
+FAIL: gcc.target/i386/pr21291.c (internal compiler error)
+FAIL: gcc.target/i386/pr21291.c (test for excess errors)

These are constrain_operands(1) failures in check_rtl. Apparently some
relevant info is lost in lra_update_insn_recog_data. Not sure how to
debug this...

Ciao!
Steven

  reply	other threads:[~2013-01-22  9:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-17 23:45 Steven Bosscher
2013-01-18  0:00 ` Jakub Jelinek
2013-01-18 19:32   ` Steven Bosscher
2013-01-19  0:15 ` Vladimir Makarov
2013-01-19 16:57   ` Steven Bosscher
2013-01-21 16:23     ` Vladimir Makarov
2013-01-22  9:42       ` Steven Bosscher [this message]
2013-01-23 18:43         ` Vladimir Makarov
2013-01-24 10:31           ` Steven Bosscher

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='CABu31nP41G7Ck5qejfad2EjQd8FgYL_SZf2YZ3guahK=WBOLWg@mail.gmail.com' \
    --to=stevenb.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=vmakarov@redhat.com \
    /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).