This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] Improve PR30911 and PR31023, Ada and VRP
- From: Duncan Sands <duncan dot sands at math dot u-psud dot fr>
- To: gcc-patches at gcc dot gnu dot org
- Cc: Richard Kenner <kenner at vlsi1 dot ultra dot nyu dot edu>, ebotcazou at adacore dot com, rguenther at suse dot de
- Date: Wed, 2 Apr 2008 11:57:28 +0200
- Subject: Re: [PATCH] Improve PR30911 and PR31023, Ada and VRP
- References: <Pine.LNX.4.64.0803291749290.4133@zhemvz.fhfr.qr> <200804011818.20620.duncan.sands@math.u-psud.fr> <10804012153.AA01066@vlsi1.ultra.nyu.edu>
> I wasn't talking about that one, but about a restrictions Pragma that
> exists to enforce a coding standard requiring initializations.
I see. I couldn't find any such pragma in the docs, is this a new feature?
> Normalize_Scalars is an interesting case, but one that I haven't thought
> about much. But, thinking aloud, in that case we know that either the
> value is in the range of the subtype or ONE SPECIFIC invalid value. That
> means the issue we were talking about where the value might be different
> in two places might not be able to occur, but I'm not sure.
I thought the issue was whether integer types with restricted ranges should
be eliminated from the middle-end in favour of __builtin_assume. As for the
pragma that requires initialization, presumably in this case most range checks
wouldn't be needed, so the front-end could simply not generate them in the
first place.
Ciao,
Duncan.