From: Segher Boessenkool <segher@kernel.crashing.org>
To: gcc-patches@gcc.gnu.org
Cc: Segher Boessenkool <segher@kernel.crashing.org>
Subject: [PATCH 0/3] Default LRA to "on"
Date: Mon, 12 Sep 2016 22:22:00 -0000 [thread overview]
Message-ID: <cover.1473715747.git.segher@kernel.crashing.org> (raw)
All primary platforms default to LRA now, not the old reload. It is too
early to remove reload (and all ports still using reload ;-) ), this will
take time, but as a first step this series makes LRA used by default.
It should not change behaviour for any existing port, only for new ports.
After the patches, ports that always want LRA do not have to define
anything, where currently ports that never want LRA define nothing.
This series is not exhaustively tested. Is it okay for trunk though?
Segher
next reply other threads:[~2016-09-12 22:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 22:22 Segher Boessenkool [this message]
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
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=cover.1473715747.git.segher@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=gcc-patches@gcc.gnu.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).