This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Signed int overflow behavior in the security context
- From: prj at po dot cwru dot edu (Paul Jarc)
- To: Paul Schlie <schlie at comcast dot net>
- Cc: <gcc at gcc dot gnu dot org>
- Date: Sun, 28 Jan 2007 01:40:00 -0500
- Subject: Re: Signed int overflow behavior in the security context
- References: <C1E1A9A4.FB15%schlie@comcast.net>
Paul Schlie <schlie@comcast.net> wrote:
> your corresponding supporting standard citation to the contrary?
C99 3.17.2 defines "indeterminate value" as "either an unspecified
value or a trap representation". 6.2.6.1p5 says of trap
representations: "If the stored value of an object has such a
representation and is read by an lvalue expression that does not have
character type, the behavior is undefined." Possibly other parts of
the standard also also make it undefined behavior to access an
uninitialized character-type variable; I haven't looked too closely.
paul