This is the mail archive of the
mailing list for the GCC project.
Re: [middle-end] PR c/29092, vector types not compatible when they should be
- From: Andrew Pinski <pinskia at physics dot uc dot edu>
- To: roger at eyesopen dot com (Roger Sayle)
- Cc: paolo dot bonzini at lu dot unisi dot ch (Paolo Bonzini), gcc-patches at gcc dot gnu dot org (GCC Patches)
- Date: Thu, 28 Sep 2006 23:40:51 -0400 (EDT)
- Subject: Re: [middle-end] PR c/29092, vector types not compatible when they should be
> Hi Paolo,
> On Wed, 27 Sep 2006, Paolo Bonzini wrote:
> > 2006-09-25 Paolo Bonzini <email@example.com>
> > PR c/29092
> > * tree.c (make_vector_type): Memoize types.
> > (used_vector_types): New.
> Hmm. I'm not really happy with the way that you're using the front-end
> specific types_compatible_p langhook to decide whether to create a new
> VECTOR_TYPE node or not. The middle-end, and particulary new type
> construction in tree.c has/needs a stricter type system...
Shouldn't this be more like what we do for arrays? Note I have not
looked into how we deal with arrays but I know that we can do
make_array_type and have it return the same array type twice.