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: basic VRP min/max range overflow question

From: Robert Dewar <dewar at adacore dot com>
To: Paul Schlie <schlie at comcast dot net>
Cc: "Joseph S. Myers" <joseph at codesourcery dot com>, Dale Johannesen <dalej at apple dot com>,Mike Stump <mrs at apple dot com>, Andrew Pinski <pinskia at physics dot uc dot edu>, GCC Development <gcc at gcc dot gnu dot org>
Date: Mon, 20 Jun 2005 07:33:49 -0400
Subject: Re: basic VRP min/max range overflow question
References: <BEDC2009.A8CF%schlie@comcast.net>

Paul Schlie wrote:

I too believe I understand your position, however don't believe it's the
compiler's job to make life for the programmer harder than it need be when
a program may contain an undefined behavior; but agree it would likely
always be helpful to for it to point them out when identifiable.


I really don't care too much about making life harder for the programmer
who originally writes code if it makes it easier for people maintaining
and porting the code down the line. I think it is a good idea if people
writing C know C (substitute any other language you like for C here :-)

Follow-Ups:
- Re: basic VRP min/max range overflow question
  - From: Paul Schlie

References:
- Re: basic VRP min/max range overflow question
  - From: Paul Schlie

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