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: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
To: fw at deneb dot enyo dot de
Cc: gcc at gcc dot gnu dot org
Date: Mon, 30 May 05 17:32:37 EDT
Subject: Re: Stickiness of TYPE_MIN_VALUE/TYPE_MAX_VALUE

    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?  

My feeling is yes, it does.

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