From: Jeff Law <law@redhat.com>
To: Michael Meissner <meissner@linux.vnet.ibm.com>,
GCC mailing list <gcc@gcc.gnu.org>,
Segher Boessenkool <segher@kernel.crashing.org>,
David Edelsohn <dje.gcc@gmail.com>, Jan Hubicka <hubicka@ucw.cz>,
Uros Bizjak <ubizjak@gmail.com>,
Kirill Yukhin <kirill.yukhin@gmail.com>,
Richard Biener <rguenther@suse.de>,
Richard Henderson <rth@redhat.com>,
Jakub Jelinek <jakub@redhat.com>,
Richard Earnshaw <richard.earnshaw@arm.com>,
Marcus Shawcroft <marcus.shawcroft@arm.com>,
Nick Clifton <nickc@redhat.com>,
Ramana Radhakrishnan <ramana.radhakrishnan@arm.com>,
Bernd Schmidt <bschmidt@redhat.com>,
Hartmut Penner <hepenner@us.ibm.com>,
Ulrich Weigand <uweigand@de.ibm.com>,
Andreas Krebbel <Andreas.Krebbel@de.ibm.com>,
Evgeny Stupachenko <evstupac@gmail.com>
Subject: Re: GCC target_clone support
Date: Fri, 05 May 2017 20:17:00 -0000 [thread overview]
Message-ID: <d955ea61-ffec-4355-93fa-a151d8740945@redhat.com> (raw)
In-Reply-To: <20170505181859.GA11428@ibm-tiger.the-meissners.org>
On 05/05/2017 12:18 PM, Michael Meissner wrote:
> I'm in the middle of adding support for the target_clone attribute to the
> PowerPC. At the moment, the x86_64/i386 port is the only port that supports
> target_clone. I added the arm/s390 port maintainers to this query, because
> those ports might also consider supporting target_clones in the future.
>
> In doing the work, I noticed that some of the functions called by the target
> hooks that were fairly generic, and we might want to move these functions into
> common code? Would people object if I put out a patch to move these functions
> to common code?
Sounds wise to me -- as you know its not unusual to find commonality
when a feature is enabled on a new target.
>
> I also have a question on the functionality of target_clone that I will address
> in a separate message.
>
> So far, the list of generic code that could be moved to common code to allow
> other ports to add target_clone support include:Please consider this class of changes pre-approved. There's no reason
to wait for review as you move this stuff around and generalize it slightly.
jeff
prev parent reply other threads:[~2017-05-05 20:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-05 18:19 Michael Meissner
2017-05-05 18:45 ` GCC target_clone support (functionality question) Michael Meissner
[not found] ` <CAOvf_xzMMbbQ+adZ+hWYtxACn_6yS50nhhcVYeBuPnUKZNPc2g@mail.gmail.com>
2017-05-05 19:48 ` Michael Meissner
[not found] ` <CAOvf_xyeUdFnfXMszOb8ZcEava+pRmzTP2naErd5U8sr2E1xpw@mail.gmail.com>
2017-05-05 20:50 ` Michael Meissner
[not found] ` <87tw4y7adg.fsf@linaro.org>
2017-05-08 22:14 ` Jeff Law
2017-05-05 18:52 ` GCC target_clone support Michael Meissner
2017-05-05 20:17 ` Jeff Law [this message]
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=d955ea61-ffec-4355-93fa-a151d8740945@redhat.com \
--to=law@redhat.com \
--cc=Andreas.Krebbel@de.ibm.com \
--cc=bschmidt@redhat.com \
--cc=dje.gcc@gmail.com \
--cc=evstupac@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=hepenner@us.ibm.com \
--cc=hubicka@ucw.cz \
--cc=jakub@redhat.com \
--cc=kirill.yukhin@gmail.com \
--cc=marcus.shawcroft@arm.com \
--cc=meissner@linux.vnet.ibm.com \
--cc=nickc@redhat.com \
--cc=ramana.radhakrishnan@arm.com \
--cc=rguenther@suse.de \
--cc=richard.earnshaw@arm.com \
--cc=rth@redhat.com \
--cc=segher@kernel.crashing.org \
--cc=ubizjak@gmail.com \
--cc=uweigand@de.ibm.com \
/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).