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: Ada subtypes and base types

From: Jeffrey A Law <law at redhat dot com>
To: Sebastian Pop <sebastian dot pop at cri dot ensmp dot fr>
Cc: Richard Kenner <kenner at vlsi1 dot ultra dot nyu dot edu>, gcc at gcc dot gnu dot org
Date: Mon, 27 Feb 2006 11:23:26 -0700
Subject: Re: Ada subtypes and base types
References: <10602241616.AA08086@vlsi1.ultra.nyu.edu> <20060224174211.GA4315@napoca.cri.ensmp.fr> <1140804942.2856.12.camel@localhost.localdomain> <20060224184736.GB5239@napoca.cri.ensmp.fr>
Reply-to: law at redhat dot com

On Fri, 2006-02-24 at 19:47 +0100, Sebastian Pop wrote:
> Jeffrey A Law wrote:
> > Another possibility is to simply not allow conversions between a
> > subtype and basetype. 
> 
> Such a patch also solves the problem.  But I'm not sure to understand
> the impact on other codes.  Is this kind of conversion between a type
> and its basetype specific to Ada?
My suspicions appear to be correct.  This never triggers except for
Ada code and it's relatively common in Ada code.  No surprise since
I don't think any other front-end abuses TYPE_MAX_VALUE in the way
the Ada front-end does.  This wouldn't be the first time we've had
to hack up something in the generic optimizers to deal with the
broken TYPE_MAX_VALUE.

jeff

Follow-Ups:
- Re: Ada subtypes and base types
  - From: Sebastian Pop

References:
- Re: Ada subtypes and base types
  - From: Richard Kenner
- Re: Ada subtypes and base types
  - From: Sebastian Pop
- Re: Ada subtypes and base types
  - From: Jeffrey A Law
- Re: Ada subtypes and base types
  - From: Sebastian Pop

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