public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bernd Edlinger <bernd.edlinger@hotmail.de>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: Vladimir Makarov <vmakarov@redhat.com>,
	Richard Biener	<rguenther@suse.de>, Jeff Law <law@redhat.com>
Subject: [PING] [PATCH] Fix asm X constraint (PR inline-asm/59155)
Date: Mon, 06 Jun 2016 13:33:00 -0000	[thread overview]
Message-ID: <AM4PR07MB157148DEF55A9C540991A296E45C0@AM4PR07MB1571.eurprd07.prod.outlook.com> (raw)
In-Reply-To: <AM4PR07MB157116B6325547B97D4C148CE4400@AM4PR07MB1571.eurprd07.prod.outlook.com>

Ping...

see https://gcc.gnu.org/ml/gcc-patches/2016-05/msg02010.html

Thanks
Bernd.


On 05/25/16 14:58, Bernd Edlinger wrote:
> Hi!
>
> This restricts the X constraint in asm statements, which
> can be easily folded by combine in something completely
> invalid.
>
> It is necessary to allow scratch here, because on i386
> the md_asm_adjust hook inserts them.
>
> The second test case fails because lra does not
> allow all register for anything_ok operands (aka X)
> and later it fails to match the two X constraints
> in case '0': if (curr_alt[m] == NO_REGS) break.
>
> There is also an identical bug in the reload pass,
> but I do not know how to fix that, as it is almost
> used nowhere today.
>
>
> Boot-strapped and regression-tested on x86_64-pc-linux-gnu.
> OK for trunk?
>
>
> Thanks
> Bernd.
>

  reply	other threads:[~2016-06-06 13:33 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-25 13:45 Bernd Edlinger
2016-06-06 13:33 ` Bernd Edlinger [this message]
2016-06-06 17:04   ` [PING] " Vladimir Makarov
2016-06-06 17:54     ` Jeff Law
2016-06-06 18:01       ` Jakub Jelinek
2016-06-06 18:04         ` Jeff Law
2016-06-06 18:09           ` Jakub Jelinek
2016-06-06 19:28             ` Marc Glisse
2016-06-06 19:40               ` Jakub Jelinek
2016-06-09 16:30                 ` Jeff Law
2016-06-09 16:43                   ` Jakub Jelinek
2016-06-09 16:45                     ` Jakub Jelinek
2016-06-10 14:13                       ` Bernd Edlinger
2016-06-19 13:25                         ` [PING**2] " Bernd Edlinger
2016-06-22 19:51                           ` Jeff Law
2016-06-22 20:49                             ` Bernd Edlinger
2016-07-20 20:04                               ` Jeff Law
2016-07-21 16:30                                 ` Bernd Edlinger
2016-08-04 20:27                                   ` Jeff Law
2016-08-05 13:30                                     ` Bernd Edlinger
2016-06-20 22:06                       ` [PING] " Jeff Law
2016-06-21  1:52                         ` Bernd Edlinger
2016-06-07 17:58             ` Bernd Edlinger
2016-06-09 16:28               ` Jeff Law

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=AM4PR07MB157148DEF55A9C540991A296E45C0@AM4PR07MB1571.eurprd07.prod.outlook.com \
    --to=bernd.edlinger@hotmail.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=law@redhat.com \
    --cc=rguenther@suse.de \
    --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).