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 19:56:04 -0500
- Subject: Re: Signed int overflow behavior in the security context
- References: <C1E2AD65.FB2D%schlie@comcast.net>
Paul Schlie <schlie@comcast.net> wrote:
> x = x ; perfectly fine; as lvaue x clearly designates an object (no trap)
Can you cite the part of the standard that says that? The fact that
an expression designates an object does not exclude that object from
holding a trap representation. A trap representation, as defined by
the standard (6.2.6.1p5), is unrelated to dereferencing an invalid
pointer. The word "trap" is also sometimes used to refer to
dereferencing an invalid pointer, but that's not relevant here, since
the standard uses a different definition.
paul