[gentoo-ppc-dev] gcc-3.2.3-r2 and altivec

[gentoo-ppc-dev] gcc-3.2.3-r2 and altivec

[Magnus Damm]

Hi there,

I recently added a gcc workaround to ffmpeg/libavcodec to cope 
with the altivec problems found in gcc-3 prior gcc-3.3.
However, yesterday I upgraded my gcc to gcc-3.2.3-r2 and now I'm 
unable to compile mplayer/libavcodec because my workaround fails.

Here's a pointer to my workaround:

http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/ffmpeg/ffmpeg/libavcodec/ppc/gcc_fixes.h

I had a look at the altivec.h-file that comes with gcc and I saw 
the same workaround there now. This fix is gentoo-specific, right?

Maybe a more fine-grained test should be better.
Or maybe renaming the functions in gcc_fixes.h will work...
Any suggestions how I should cope with this issue?

/ magnus

--
gentoo-ppc-dev@gentoo.org mailing list

Re: [gentoo-ppc-dev] gcc-3.2.3-r2 and altivec

[Bartosch Pixa]

[-- Attachment #1: Type: text/plain, Size: 175 bytes --]

well basicaly with our fixed gcc you shouldn't need your ffmpeg fix
anymore.

regards
-- 
Bartosch Pixa
Gentoo Linux Developer                    http://www.gentoo.org

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-ppc-dev] gcc-3.2.3-r2 and altivec

[Magnus Damm]

On 27 Jul 2003 19:00:03 +0200
Bartosch Pixa <darkspecter@gentoo.org> wrote:

> well basicaly with our fixed gcc you shouldn't need your ffmpeg fix
> anymore.

I understand that, but how do I know that the version of gcc I run
is the pristine "buggy" gcc or if it's patched with the gentoo-patches?
Is some gentoo-specific constant set that I could check?

Well, never mind - I could change the symbols used by my workaround.
That solves it, but I wonder if that is the right thing(tm).
The right way would probably be to check for buggy altivec in configure.

Thanks.

/ magnus

--
gentoo-ppc-dev@gentoo.org mailing list

Re: [gentoo-ppc-dev] gcc-3.2.3-r2 and altivec

[Luca Barbato]

Well, basically ffmpeg people use my fix in their code.
Sadly they didn't change the name of the static functions...
(Credits to the original idea are due to Michel Lespinasse, I just 
extended the vpem->mergel to the other datatype.)

If you want to remove or change the fix I put just edit your altivec.h 
include changing the function names.

Regards


Magnus Damm wrote:
> On 27 Jul 2003 19:00:03 +0200
> Bartosch Pixa <darkspecter@gentoo.org> wrote:
> 
> 
>>well basicaly with our fixed gcc you shouldn't need your ffmpeg fix
>>anymore.
> 
> 
> I understand that, but how do I know that the version of gcc I run
> is the pristine "buggy" gcc or if it's patched with the gentoo-patches?
> Is some gentoo-specific constant set that I could check?
> 
> Well, never mind - I could change the symbols used by my workaround.
> That solves it, but I wonder if that is the right thing(tm).
> The right way would probably be to check for buggy altivec in configure.
> 
> Thanks.
> 
> / magnus
> 
> --
> gentoo-ppc-dev@gentoo.org mailing list
> 
> 


-- 
Luca Barbato
Developer
Gentoo Linux				http://www.gentoo.org/~lu_zero




--
gentoo-ppc-dev@gentoo.org mailing list