From: Jeff Law <law@redhat.com>
To: Bernd Edlinger <bernd.edlinger@hotmail.de>,
Jakub Jelinek <jakub@redhat.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Vladimir Makarov <vmakarov@redhat.com>,
Richard Biener <rguenther@suse.de>
Subject: Re: [PING**2] [PATCH] Fix asm X constraint (PR inline-asm/59155)
Date: Wed, 22 Jun 2016 19:51:00 -0000 [thread overview]
Message-ID: <fe016e9b-ee15-6532-a1d4-40558849030a@redhat.com> (raw)
In-Reply-To: <AM4PR0701MB2162A54B3CAFABC7BE6FD859E4290@AM4PR0701MB2162.eurprd07.prod.outlook.com>
On 06/19/2016 07:25 AM, Bernd Edlinger wrote:
> Hi,
>
> ping...
>
> As this discussion did not make any progress, I just attached
> the latest version of my patch with the the changes that
> Vladimir proposed.
>
> Boot-strapped and reg-tested again on x86_64-linux-gnu.
> Is it OK for the trunk?
Well, I don't think we've got any kind of consensus on whether or not
this is reasonable or not.
The fundamental issue is that "X" is supposed to accept anything,
literally anything. That implies it's really the downstream users of
those operands that are broken.
Jeff
next prev parent reply other threads:[~2016-06-22 19:51 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 ` [PING] " Bernd Edlinger
2016-06-06 17:04 ` 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 [this message]
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=fe016e9b-ee15-6532-a1d4-40558849030a@redhat.com \
--to=law@redhat.com \
--cc=bernd.edlinger@hotmail.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@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).