From: Joseph Myers <joseph@codesourcery.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Bernd Schmidt <bschmidt@redhat.com>, <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 1/3] Put a TARGET_LRA_P into every target
Date: Tue, 13 Sep 2016 16:23:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1609131613360.9352@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20160913110349.GA18438@gate.crashing.org>
On Tue, 13 Sep 2016, Segher Boessenkool wrote:
> Yes, many targets need the hook definition after this series; that should
> stick out like a sore thumb, help to remind people to change their target
> to use LRA (not a huge amount of work for most, although it can get tricky).
I would also encourage an email to all the maintainers of ports using
reload, CC gcc@, pointing out that moving is desirable and with pointers
to guidance on how to do the move.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2016-09-13 16:16 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
2016-09-13 16:08 ` Jeff Law
2016-09-13 17:08 ` Mike Stump
2016-09-13 16:23 ` Joseph Myers [this message]
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=alpine.DEB.2.20.1609131613360.9352@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=bschmidt@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).