This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: Giving hints to the compiler/optimizer (#pragma hint ...)
- From: Jonathan Wakely <jwakely dot gcc at gmail dot com>
- To: um at mutluit dot com
- Cc: gcc-help <gcc-help at gcc dot gnu dot org>
- Date: Fri, 22 Jun 2018 12:27:39 +0100
- Subject: Re: Giving hints to the compiler/optimizer (#pragma hint ...)
- References: <5B2C97EA.7050001@mutluit.com> <CAH6eHdSPJXDPB0QwMWZfxy0_0Sk+2eH_oc0Tz60iMSA3d08=Lg@mail.gmail.com> <5B2CD0E9.8040509@mutluit.com>
On Fri, 22 Jun 2018 at 11:35, U.Mutlu wrote:
>
> Jonathan Wakely wrote on 06/22/2018 11:42 AM:
> > On Fri, 22 Jun 2018 at 07:32, U.Mutlu wrote:
> >> (The manual version has of course the disadvantage that user has to define an
> >> additional variable and because of that, put the code in its own scope...)
> >
> > You don't have to change the scope:
> >
> > for (size_t i = 1, vec_sz = vec.size(); i < vec_sz; ++i)
>
> Yes, I know that, but it lacks the "const" attribute.
Does it matter? The compiler can still see it doesn't change.