From: Segher Boessenkool <segher@kernel.crashing.org>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] rs6000: Add "cannot_copy" attribute, use it (PR67788, PR67789)
Date: Thu, 01 Oct 2015 17:39:00 -0000 [thread overview]
Message-ID: <20151001173926.GA1870@gate.crashing.org> (raw)
In-Reply-To: <CAGWvnynh4og-d6ZUrFS7zJPTuYe2aQr6+xv=FA9FjO7EC3otuQ@mail.gmail.com>
On Thu, Oct 01, 2015 at 10:08:50AM -0400, David Edelsohn wrote:
> Is this expensive enough that it is worth limiting the definition of
> the hook to configurations that include 32-bit SVR4 support so that
> not every configuration incurs the overhead?
I don't think so. That won't save the call to the target hook, and
that is a big part of the overhead already.
Segher
prev parent reply other threads:[~2015-10-01 17:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 6:09 Segher Boessenkool
2015-10-01 10:14 ` Richard Biener
2015-10-01 11:12 ` Bernd Schmidt
2015-10-01 17:18 ` Segher Boessenkool
2015-10-02 0:54 ` Alan Modra
2015-10-02 1:15 ` Segher Boessenkool
2015-10-02 8:31 ` Richard Biener
2015-10-01 14:05 ` David Edelsohn
2015-10-01 14:08 ` David Edelsohn
2015-10-01 17:39 ` Segher Boessenkool [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=20151001173926.GA1870@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=dje.gcc@gmail.com \
--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).