This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Implementing VMX128 AltiVec Variant
- From: Ian Lance Taylor <iant at google dot com>
- To: Gordan Bobic <gordan at bobich dot net>
- Cc: gcc at gcc dot gnu dot org
- Date: 21 Aug 2007 15:02:37 -0700
- Subject: Re: Implementing VMX128 AltiVec Variant
- References: <46CB5DF7.7000604@bobich.net>
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.
> 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.
Ian