public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: Segher Boessenkool <segher@kernel.crashing.org>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 1/3] Put a TARGET_LRA_P into every target
Date: Tue, 13 Sep 2016 20:39:00 -0000	[thread overview]
Message-ID: <f203dcf0-53b0-40ef-2267-4282704ba37e@redhat.com> (raw)
In-Reply-To: <b0b52629100d9587f1cce915fdf65b5e6dc03497.1473715747.git.segher@kernel.crashing.org>

On 09/12/2016 04:22 PM, Segher Boessenkool wrote:
> This patch adds a TARGET_LRA_P (defined to hook_bool_void_false) to
> every target that didn't yet override the hook.  No functional change.
>
>
> Segher
>
>
> 2016-09-12  Segher Boessenkool  <segher@kernel.crashing.org>
>
> 	* config/alpha/alpha.c (TARGET_LRA_P): New macro, defined to
> 	hook_bool_void_false.
> 	* config/avr/avr.c: Ditto.
> 	* config/bfin/bfin.c: Ditto.
> 	* config/c6x/c6x.c: Ditto.
> 	* config/cr16/cr16.c: Ditto.
> 	* config/cris/cris.c: Ditto.
> 	* config/epiphany/epiphany.c: Ditto.
> 	* config/fr30/fr30.c: Ditto.
> 	* config/frv/frv.c: Ditto.
> 	* config/h8300/h8300.c: Ditto.
> 	* config/ia64/ia64.c: Ditto.
> 	* config/iq2000/iq2000.c: Ditto.
> 	* config/lm32/lm32.c: Ditto.
> 	* config/m32c/m32c.c: Ditto.
> 	* config/m32r/m32r.c: Ditto.
> 	* config/m68k/m68k.c: Ditto.
> 	* config/mcore/mcore.c: Ditto.
> 	* config/microblaze/microblaze.c: Ditto.
> 	* config/mmix/mmix.c: Ditto.
> 	* config/mn10300/mn10300.c: Ditto.
> 	* config/moxie/moxie.c: Ditto.
> 	* config/msp430/msp430.c: Ditto.
> 	* config/nios2/nios2.c: Ditto.
> 	* config/nvptx/nvptx.c: Ditto.
> 	* config/pa/pa.c: Ditto.
> 	* config/pdp11/pdp11.c: Ditto.
> 	* config/rl78/rl78.c: Ditto.
> 	* config/sparc/sparc.c: Ditto.
> 	* config/spu/spu.c: Ditto.
> 	* config/stormy16/stormy16.c: Ditto.
> 	* config/tilegx/tilegx.c: Ditto.
> 	* config/tilepro/tilepro.c: Ditto.
> 	* config/v850/v850.c: Ditto.
> 	* config/vax/vax.c: Ditto.
> 	* config/visium/visium.c: Ditto.
> 	* config/xtensa/xtensa.c: Ditto.
I believe a doc update of some kind is in order.  With the doc update 
the entire series is OK.
jeff

  parent reply	other threads:[~2016-09-13 20:39 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-12 22:22 [PATCH 0/3] Default LRA to "on" Segher Boessenkool
2016-09-12 22:22 ` [PATCH 2/3] Change the default of TARGET_LRA_P to true Segher Boessenkool
2016-09-12 22:22 ` [PATCH 1/3] Put a TARGET_LRA_P into every target Segher Boessenkool
2016-09-13 10:42   ` Bernd Schmidt
2016-09-13 11:11     ` Segher Boessenkool
2016-09-13 14:27       ` Andrew Pinski
2016-09-13 15:53         ` Peter Bergner
2016-09-13 16:08           ` Jeff Law
2016-09-13 17:08             ` Mike Stump
2016-09-13 16:23       ` Joseph Myers
2016-09-13 20:07         ` Segher Boessenkool
2016-09-13 16:02     ` Jeff Law
2016-09-13 20:39   ` Jeff Law [this message]
2016-09-14 11:06     ` Segher Boessenkool
2016-09-14 13:01       ` Peter Bergner
2016-09-14 14:01         ` Segher Boessenkool
2016-09-16 10:39       ` Gerald Pfeifer
2016-09-16 13:34         ` Richard Kenner
2016-09-16 14:35         ` Segher Boessenkool
2016-09-16 19:46           ` Mike Stump
2016-09-19 15:55             ` Segher Boessenkool
2016-09-12 22:28 ` [PATCH 3/3] Delete TARGET_LRA_P from those targets that set it to "true" 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=f203dcf0-53b0-40ef-2267-4282704ba37e@redhat.com \
    --to=law@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=segher@kernel.crashing.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).