From: Richard Guenther <richard.guenther@gmail.com>
To: Michael Matz <matz@suse.de>,
gcc-patches@gcc.gnu.org, richard.sandiford@linaro.org
Subject: Re: RFC: explicitely mark out-of-scope deaths
Date: Wed, 01 Jun 2011 09:44:00 -0000 [thread overview]
Message-ID: <BANLkTi=MzAMFvQoDbpAoDXXFxaGte=BhYQ@mail.gmail.com> (raw)
In-Reply-To: <g4hb89gayu.fsf@linaro.org>
On Wed, Jun 1, 2011 at 11:25 AM, Richard Sandiford
<richard.sandiford@linaro.org> wrote:
> Michael Matz <matz@suse.de> writes:
>> Stores are better than builtin functions here, so as to not artificially
>> take addresses of the decls in question.
>
> For the record, you wouldn't need to take the address if you had an
> internal function (internal-fn.def) of the form:
>
> MEM_REF [<thing to clobber>] = internal_fn_that_returns_unknown_data ();
>
> This was one of the reasons for adding internal functions, and we use
> a similar technique for the interleaved load/stores.
>
> Not an argument in favour of using calls. There are probably other
> reasons to prefer your representation. It just seemed that, whatever
> the arguments against using calls are, taking the address doesn't
> need to be one of them.
True at least since we have internal functions ;) Still an aggregate
assignment looks less disturbing to random optimizers than a call.
Richard.
prev parent reply other threads:[~2011-06-01 9:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 14:30 Michael Matz
2011-05-26 15:07 ` Jakub Jelinek
2011-05-26 15:17 ` Richard Guenther
2011-05-26 17:38 ` Steven Bosscher
2011-05-27 15:44 ` Michael Matz
2011-05-27 15:49 ` Jakub Jelinek
2011-05-27 16:45 ` Michael Matz
2011-05-26 23:49 ` Martin Jambor
2011-05-27 13:24 ` Michael Matz
2011-06-01 9:25 ` Richard Sandiford
2011-06-01 9:44 ` Richard Guenther [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='BANLkTi=MzAMFvQoDbpAoDXXFxaGte=BhYQ@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=matz@suse.de \
--cc=richard.sandiford@linaro.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).