From: Ian Lance Taylor <iant@google.com>
To: Ulf Magnusson <ulfalizer@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Suboptimal __restrict optimization?
Date: Mon, 03 Oct 2011 20:23:00 -0000 [thread overview]
Message-ID: <mcrd3edzuy6.fsf@coign.corp.google.com> (raw)
In-Reply-To: <CAFkk2KTGL53aWgNiNQm8+Yt_6SK2nXjPDonpH4fT9Mp_PWoJTw@mail.gmail.com> (Ulf Magnusson's message of "Sun, 2 Oct 2011 02:58:43 +0200")
Ulf Magnusson <ulfalizer@gmail.com> writes:
> Is there some reason why GCC couldn't generate this code for the first
> version of C::f()? Is this a failure of optimization, or am I missing
> something in how __restricted works?
It's a failure of optimization.
Ian
next prev parent reply other threads:[~2011-10-03 20:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-02 0:59 Ulf Magnusson
2011-10-03 20:23 ` Ian Lance Taylor [this message]
2011-10-04 15:08 ` Ulf Magnusson
2011-10-04 15:47 ` Richard Guenther
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=mcrd3edzuy6.fsf@coign.corp.google.com \
--to=iant@google.com \
--cc=gcc@gcc.gnu.org \
--cc=ulfalizer@gmail.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).