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]

Re: Stickiness of TYPE_MIN_VALUE/TYPE_MAX_VALUE

From: Geert Bosch <bosch at adacore dot com>
To: Florian Weimer <fw at deneb dot enyo dot de>
Cc: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner), gcc at gcc dot gnu dot org
Date: Tue, 31 May 2005 07:24:16 -0400
Subject: Re: Stickiness of TYPE_MIN_VALUE/TYPE_MAX_VALUE
References: <10505302005.AA08879@vlsi1.ultra.nyu.edu> <8764x0o2ui.fsf@deneb.enyo.de>

On May 30, 2005, at 16:50, Florian Weimer wrote:

I'll try to phrase it differently: If you access an object whose bit
pattern does not represent a value in the range given by
TYPE_MIN_VALUE .. TYPE_MAX_VALUE of the corresponding type, does this
result in erroneous execution/undefined behavior?  If not, what is the
exact behavior WRT to out-of-bounds values?


This is correct. Note that this is only valid for objects,
in expressions intermediate values may lay outside the range
of the type.

References:
- Re: Stickiness of TYPE_MIN_VALUE/TYPE_MAX_VALUE
  - From: Richard Kenner
- Re: Stickiness of TYPE_MIN_VALUE/TYPE_MAX_VALUE
  - From: Florian Weimer

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]