This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Suboptimal __restrict optimization?

From: Ulf Magnusson <ulfalizer at gmail dot com>
To: Ian Lance Taylor <iant at google dot com>
Cc: gcc at gcc dot gnu dot org
Date: Tue, 4 Oct 2011 17:07:46 +0200
Subject: Re: Suboptimal __restrict optimization?
References: <CAFkk2KTGL53aWgNiNQm8+Yt_6SK2nXjPDonpH4fT9Mp_PWoJTw@mail.gmail.com> <mcrd3edzuy6.fsf@coign.corp.google.com>

On Mon, Oct 3, 2011 at 10:22 PM, Ian Lance Taylor <iant@google.com> wrote:
> 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
>

Is this something that has been improved in 4.6.x? (Sorry for the
initial non-reply-all.)

Follow-Ups:
- Re: Suboptimal __restrict optimization?
  - From: Richard Guenther

References:
- Suboptimal __restrict optimization?
  - From: Ulf Magnusson
- Re: Suboptimal __restrict optimization?
  - From: Ian Lance Taylor

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]