public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Sandiford <rdsandiford@googlemail.com>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: David Malcolm <dmalcolm@redhat.com>,  gcc-patches@gcc.gnu.org
Subject: Re: [buildrobot] [PATCH] mips: Really remove ENTRY_BLOCK_PTR
Date: Wed, 20 Nov 2013 10:13:00 -0000	[thread overview]
Message-ID: <87iovn8mq2.fsf@talisman.default> (raw)
In-Reply-To: <20131120090429.GT30563@lug-owl.de> (Jan-Benedict Glaw's message	of "Wed, 20 Nov 2013 10:04:29 +0100")

Jan-Benedict Glaw <jbglaw@lug-owl.de> writes:
> 2013-11-20  Jan-Benedict Glaw  <jbglaw@lug-owl.de>
>
> 	* config/mips/mips.c (r10k_simplify_address): Eliminate macro usage.

OK.  And thanks for the catch.

Richard

  reply	other threads:[~2013-11-20  9:08 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-20 10:07 Jan-Benedict Glaw
2013-11-20 10:13 ` Richard Sandiford [this message]
2013-11-20 10:15 ` Steven Bosscher
2013-11-20 12:13   ` Jan-Benedict Glaw
2013-11-20 18:40     ` [PATCH] Fix comments that refer to ENTRY_{BLOCK|EXIT}_PTR David Malcolm
2013-11-20 19:05       ` Jeff Law
2013-11-21  9:18         ` David Malcolm
2013-11-26 19:39         ` Michael Matz
2013-11-26  8:42   ` gcc's obvious patch policy Alan Modra
2013-11-26  9:59     ` Steven Bosscher
     [not found]       ` <20131126102146.GA9211@bubble.grove.modra.org>
2013-11-27  1:52         ` David Edelsohn
2013-11-27  2:44           ` Robert Dewar
2013-11-27  8:02             ` Alan Modra
2013-11-27  8:13               ` Richard Kenner
2013-11-27  7:37           ` Alan Modra
2013-11-27  9:04             ` David Edelsohn
2013-11-26 18:34     ` Diego Novillo
2013-11-26 20:16       ` Jeff Law
2013-11-26 20:28         ` Iyer, Balaji V
2013-11-26 20:35           ` James Greenhalgh
2013-11-26 20:39           ` Eric Botcazou
2013-11-26 20:48             ` Iyer, Balaji V
2013-11-26 20:52               ` Diego Novillo
2013-11-26 20:42           ` Richard Earnshaw
2013-11-26 23:43     ` Mike Stump

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=87iovn8mq2.fsf@talisman.default \
    --to=rdsandiford@googlemail.com \
    --cc=dmalcolm@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jbglaw@lug-owl.de \
    /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).