Re: Implementing VMX128 AltiVec Variant

[Gordan Bobic <gordan at bobich dot net>]

Ian Lance Taylor wrote:
> Gordan Bobic <gordan@bobich.net> writes:
>
> > These are the only place I found references to them, apart from the
> > files in the gcc/ada directory:
> >
> > gcc/ada/g-alveop.adb
> > gcc/ada/g-alveop.ads
> > gcc/ada/g-alleve.adb
> > gcc/ada/g-alleve.ads
> >
> > I ignored these - I am making a rash assumption here that these are
> > not too important for a C/C++ only build, but I'd like some
> > confirmation on that. What are the above ada files for?
>
> I don't know what they are for, but I can confirm that they are
> irrelevant for a C/C++ build.

Just out of interest, I only downloaded the core, gcc and g++ tar balls 
of the source. Why are the above ada files in there if they are 
irrelevant for a C/C++ only build?

> > With the modifications I made, GCC still compiled fine. However,
> > libgcc and libstdc++ DO still get build with the missing instructions
> > (according to objdump -D). Why is that? Is that a consequence of the
> > ADA files? Or something else? Where should I look? Is the it ada files
> > that are the cause of the problem I'm seeing?
>
> It must be something else.  I'm not sure what, though.  It might be
> something as simple as an instruction built from substrings.  For
> example, search for altivec_vmsumu<VI_char>m in altivec.md.

Hmm, fair point. I'll have a re-check for this. I thought I weeded all 
those out, but I might have missed some.

Thanks.

Gordan