public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: Richard Henderson <rth@redhat.com>, gcc-patches@gcc.gnu.org
Cc: peterz@infradead.org, hpa@zytor.com,
	torvalds@linux-foundation.org,        jakub@redhat.com
Subject: Re: [PATCH 1/6] Only resolve_asm_operand_names once
Date: Fri, 08 May 2015 18:11:00 -0000	[thread overview]
Message-ID: <554CFC55.8090209@redhat.com> (raw)
In-Reply-To: <1431034740-5375-2-git-send-email-rth@redhat.com>

On 05/07/2015 03:38 PM, Richard Henderson wrote:
> We do it in the front end already; no need to repeat.
> ---
>   gcc/cfgexpand.c | 2 --
>   gcc/stmt.c      | 7 ++++---
>   2 files changed, 4 insertions(+), 5 deletions(-)
Any reason this shouldn't go into the tree immediately?  Seems like it 
stands on its own.

jeff

  reply	other threads:[~2015-05-08 18:11 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-07 21:39 [RFC 0/6] Flags outputs for asms Richard Henderson
2015-05-07 21:39 ` [PATCH 4/6] Convert to md_asm_adjust Richard Henderson
2015-05-08 19:41   ` Jeff Law
2015-05-08 19:56     ` Richard Henderson
2015-05-07 21:39 ` [PATCH 6/6] i386: Implement asm flag outputs Richard Henderson
2015-05-08 18:40   ` H. Peter Anvin
2015-05-08 18:45     ` Jeff Law
2015-05-15 15:46   ` [PATCH v2 " Richard Henderson
2015-05-20 16:26     ` Jeff Law
2015-05-20 16:36       ` H. Peter Anvin
2015-05-20 17:28       ` Richard Henderson
2015-05-07 21:39 ` [PATCH 2/6] Merge expand_asm_operands into expand_asm_stmt Richard Henderson
2015-05-08 18:54   ` Jeff Law
2015-05-07 21:39 ` [PATCH 1/6] Only resolve_asm_operand_names once Richard Henderson
2015-05-08 18:11   ` Jeff Law [this message]
2015-05-07 21:39 ` [PATCH 3/6] Canonicalize asm volatility earlier Richard Henderson
2015-05-08 18:12   ` Jeff Law
2015-05-07 21:39 ` [PATCH 5/6] i386: Add CCPmode Richard Henderson
2015-05-08 18:16   ` Jeff Law
2015-05-08  1:15 ` [RFC 0/6] Flags outputs for asms H. Peter Anvin
2015-05-08  1:20   ` H. Peter Anvin
2015-05-08 15:24     ` Richard Henderson
2015-05-08 15:37       ` Jay Foad
2015-05-08 15:39       ` Jeff Law
2015-05-08 15:54   ` Richard Henderson
2015-05-08 17:46     ` H. Peter Anvin
2015-05-08 20:15     ` Richard Henderson
2015-05-08 21:14       ` Segher Boessenkool
2015-05-08 22:11         ` Richard Henderson
2015-05-08 21:33       ` Jeff Law
2015-05-08 21:55         ` Richard Henderson
2015-05-08 22:10         ` Segher Boessenkool
2015-05-11 13:19       ` Segher Boessenkool

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=554CFC55.8090209@redhat.com \
    --to=law@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hpa@zytor.com \
    --cc=jakub@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rth@redhat.com \
    --cc=torvalds@linux-foundation.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).