This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: auto-vectorization
- From: ja2morri at csclub dot uwaterloo dot ca (James A. Morrison)
- To: James Cloos <cloos at jhcloos dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: 26 Oct 2004 08:57:12 -0400
- Subject: Re: auto-vectorization
- References: <m3654xlu59.fsf@lugabout.cloos.reno.nv.us>
James Cloos <cloos@jhcloos.com> writes:
> What is the status of the auto-vectorization support in 4.0?
>
> I grabbed the latest snapshot yesterday and tried compiling asterisk¹
> with it. (Incidently, before I found -ftree-vectorize in the docs,
> the 4.0-compiled codecs were slower as shown by asterisk's show
> translations command than the 3.4.2-compiled codecs.) However, with
> the -ftree-vectorize option the compiled crapped out when compiling
> certain of the codecs with an internal compiler error.
ICEs are bugs.
> Before working on a proper bug report, I wanted to find out whether
> the code is supposed to be functional, has any know issues, etc.
> Ie whether such a report is desired.
Check in bugzilla to ensure your bug hasn't already be reported. I was
able to compile ffmpeg with -ftree-vectorize -maltivec on ppc-linux with only
two files causes problems, neither caused by -ftree-vectorize.
> -JimC
>
> ¹ cf asterisk.org
>
--
Thanks,
Jim
http://www.student.cs.uwaterloo.ca/~ja2morri/
http://phython.blogspot.com
http://open.nit.ca/wiki/?page=jim