This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: changing "configure" to default to "gcc -g -O2 -fwrapv ..."
- From: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
- To: mveksler at techunix dot technion dot ac dot il
- Cc: autoconf-patches at gnu dot org, bernds_cb1 at t-online dot de, bug-gnulib at gnu dot org, dewar at adacore dot com, ebb9 at byu dot net, eggert at cs dot ucla dot edu, gcc at gcc dot gnu dot org, gdr at integrable-solutions dot net, pinskia at physics dot uc dot edu, richard dot guenther at gmail dot com
- Date: Sun, 31 Dec 2006 08:33:05 EST
- Subject: Re: changing "configure" to default to "gcc -g -O2 -fwrapv ..."
- References: <200612302357.kBUNvCPc016788@localhost.localdomain> <459701F7.8020201@adacore.com> <4597836C.3070002@tx.technion.ac.il>
> On the other hand, C does not have a way to tell the compiler:
>
> "this is my loop variable, it must not be modified inside the loop"
>
> neither you can say:
>
> "this is the upper bound of the loop, it must not be modified"
>
> either.
No, but the compiler can almost always trivially determine that nothing in
the loop can modify the variable, so I'm not sure I understand your point.