From: Jeffrey A Law <law@redhat.com>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: Mark Mitchell <mark@codesourcery.com>,
Eric Botcazou <ebotcazou@adacore.com>,
Arnaud Charlet <charlet@adacore.com>,
Richard Kenner <kenner@vlsi1.ultra.nyu.edu>,
gcc@gcc.gnu.org, Andrew Pinski <pinskia@physics.uc.edu>,
Andrew Haley <aph@redhat.com>
Subject: Re: Bootstrap failure on trunk: x86_64-linux-gnu
Date: Wed, 22 Feb 2006 16:31:00 -0000 [thread overview]
Message-ID: <1140625798.1915.26.camel@localhost.localdomain> (raw)
In-Reply-To: <84fc9c000602220251y3054e492v273a7f85b379b6cf@mail.gmail.com>
On Wed, 2006-02-22 at 11:51 +0100, Richard Guenther wrote:
> On 2/21/06, Mark Mitchell <mark@codesourcery.com> wrote:
> > Jeffrey A Law wrote:
> >
> > > My feeling? Absolutely, TYPE_MIN_VALUE and TYPE_MAX_VALUE should
> > > represent the set of values that an object of the type may hold.
> > > Any other definition effectively renders those values useless.
> >
> > I agree -- with the obvious caveat that it need not be the case that the
> > object actually have that value if the program has invoked undefined
> > behavior. So, if you have an 5-bit type, stored in a byte, and you
> > manage to get 255 in that byte, and you read the value, you might see
> > 255 at runtime -- but only because your program was busted anyhow.
>
> Right. And if Ada wants to test for this condition using 'Valid, it should do
> the range comparison in the base type and use a VIEW_CONVERT_EXPR
> to get to the object of the base type from the 5-bit-type to avoid VRP
> optimizing away the comparison.
Agreed wholeheartedly.
Jeff
next prev parent reply other threads:[~2006-02-22 16:31 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-19 17:08 Andrew Haley
2006-02-19 17:11 ` Andrew Pinski
2006-02-19 17:14 ` Arnaud Charlet
2006-02-19 19:13 ` Eric Botcazou
2006-02-21 17:35 ` Jeffrey A Law
2006-02-21 22:56 ` Mark Mitchell
2006-02-22 10:51 ` Richard Guenther
2006-02-22 16:31 ` Jeffrey A Law [this message]
2006-02-22 16:40 ` Jeffrey A Law
2006-02-22 17:00 ` Mark Mitchell
2006-02-22 17:07 ` Jeffrey A Law
2006-02-23 21:25 ` Richard Henderson
2006-02-28 11:04 ` Eric Botcazou
2006-02-28 16:48 ` Jeffrey A Law
2006-02-28 17:40 ` Eric Botcazou
2006-02-28 22:43 ` Jeffrey A Law
2006-02-28 23:59 ` Daniel Jacobowitz
2006-03-01 12:08 ` Laurent GUERBY
2006-03-01 22:35 ` Jeffrey A Law
2006-03-01 23:38 ` ACATS c460008 and VRP (was: Bootstrap failure on trunk: x86_64-linux-gnu) Laurent GUERBY
2006-03-01 23:58 ` ACATS c460008 and VRP Robert Dewar
2006-03-02 0:34 ` ACATS c460008 and VRP (was: Bootstrap failure on trunk: x86_64-linux-gnu) Eric Botcazou
2006-03-02 0:43 ` ACATS c460008 and VRP Robert Dewar
2006-03-02 13:02 ` Eric Botcazou
2006-03-02 20:00 ` Laurent GUERBY
2006-03-02 20:03 ` Eric Botcazou
2006-03-02 8:32 ` ACATS c460008 and VRP (was: Bootstrap failure on trunk: x86_64-linux-gnu) Laurent GUERBY
2007-12-05 21:20 ` Richard Kenner
2006-03-02 13:03 ` Bootstrap failure on trunk: x86_64-linux-gnu Eric Botcazou
2006-03-02 13:29 ` Eric Botcazou
2006-03-02 19:07 ` Jeffrey A Law
2006-03-02 19:12 ` Eric Botcazou
2006-03-01 10:29 ` Sebastian Pop
2006-02-28 16:57 ` Diego Novillo
2006-02-28 17:12 ` Richard Guenther
2006-02-28 17:48 ` Eric Botcazou
2006-02-28 22:43 ` Jeffrey A Law
2006-02-28 22:51 ` Diego Novillo
2006-02-28 23:21 ` Jeffrey A Law
2006-02-19 17:35 ` Andrew Haley
2006-02-19 17:20 ` Andreas Schwab
2006-02-19 19:17 Richard Kenner
2006-03-01 2:00 Richard Kenner
2006-03-01 2:02 Richard Kenner
2006-03-01 3:01 Richard Kenner
2006-03-03 8:08 ` Duncan Sands
2006-03-01 13:10 Richard Kenner
2006-03-01 13:17 Richard Kenner
2006-03-01 21:16 ` Jeffrey A Law
2006-03-02 19:09 Richard Kenner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1140625798.1915.26.camel@localhost.localdomain \
--to=law@redhat.com \
--cc=aph@redhat.com \
--cc=charlet@adacore.com \
--cc=ebotcazou@adacore.com \
--cc=gcc@gcc.gnu.org \
--cc=kenner@vlsi1.ultra.nyu.edu \
--cc=mark@codesourcery.com \
--cc=pinskia@physics.uc.edu \
--cc=richard.guenther@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).