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] | |
Then we have two switches:
-fstandard
which allows all optimizations (name can be changed, I don't care about the name)
-fwrapv
which changes the semantics to require wrapping in all cases (including loops)
What about -fno-wrapv for the first?
Possible .. my view was that it is probably not necessary to distinguish the various subcases which arise now or in the future of aggressive optimization opportunities based on assumption of strict standard semantics.
For example, for me in -fstandard, I would tolerate the "dewar password check example" being optimized to remove the password check.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |