This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Optimization of offset computations
- To: rth at cygnus dot com
- Subject: Re: Optimization of offset computations
- From: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
- Date: Tue, 30 Nov 99 21:09:36 EST
- Cc: gcc-patches at gcc dot gnu dot org
This seems reasonable. (I would use "is undefined" not "isn't
permitted" in any documentation.)
The distinction I was trying to make is that from a formal semantic point
of view overflow isn't permitted, which means that the result is undefined.
Some languages use the term "erroneous" to describe this situation.
Should get marked for C pointer arithmetic as well.
Right.
Now I'm thinking it makes more sense to have this as a flag for a
*type* rather than trying to flag all operations.