public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Peter Bergner <bergner@vnet.ibm.com>
To: Andrew Pinski <pinskia@gmail.com>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
	       Bernd Schmidt <bschmidt@redhat.com>,
	       GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 1/3] Put a TARGET_LRA_P into every target
Date: Tue, 13 Sep 2016 15:53:00 -0000	[thread overview]
Message-ID: <a67f1b44-5bef-c779-fd03-5ae7e706d76a@vnet.ibm.com> (raw)
In-Reply-To: <CA+=Sn1=D85pF8s9rL1WUZE-bNLN+n49E6gKE0TkF5prnaVy5+A@mail.gmail.com>

On 9/13/16 9:26 AM, Andrew Pinski wrote:
> On Tue, Sep 13, 2016 at 12:03 PM, Segher Boessenkool
>> And all new ports should use LRA, so it should be the default.
>
> Since nobody else has said anything on this patch besides Bernd, I am
> going to say yes please.  This patch in my mind is the right way
> forward.  In the same new ports should not be cc0 ports (though I know
> some folks try that every once in a while).

+ 1!

If we don't make LRA the default, it will be very easy for new ports
to default to reload, since they'll have to actively force usage of
LRA and I can see that point being missed even if we have it documented.
We don't want new ports to find out they need to enable LRA during
their patch submission, since that entails a huge amount of retesting.
It should be LRA from day 1 for them.

Peter


  reply	other threads:[~2016-09-13 15:45 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 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 [this message]
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
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:22 ` [PATCH 2/3] Change the default of TARGET_LRA_P to true 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=a67f1b44-5bef-c779-fd03-5ae7e706d76a@vnet.ibm.com \
    --to=bergner@vnet.ibm.com \
    --cc=bschmidt@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=pinskia@gmail.com \
    --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).