https://bugzilla.novell.com/show_bug.cgi?id=444639
User matt@genesi-usa.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=444639#c19
Matt Sealey changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pczanik@genesi-usa.com, matt@genesi-usa.com
--- Comment #19 from Matt Sealey 2008-12-31 16:23:00 MST ---
I notice a couple odd things about the latest xorg-x11-libs RPM (from src-oss
for 11.1) - that --disable-vmx is mentioned in the changes in the .spec file,
but it is never actually referenced inside the .spec file apart from that.
There are no pixman or other patches which mess with the pixman vmx detection
other than some minor fixup. I am not sure HOW the latest RPMs are actually not
built with this support weirdly enabled..
~
Ideally libpixman should not be using SIGILL traps (bad behaviour) since you
can reliably check for AltiVec at runtime without invoking any AltiVec
instructions (/proc/$self/auxv AT_HWCAP for PPC_FEATURE_HAS_ALTIVEC -
http://www.freevec.org/function/altivec_runtime_detection_linux)
Without this feature set in auxv, the kernel doesn't support AltiVec anyway and
will therefore not work. I tried to CC the VMX support author (Luca Barbato,
lu_zero@gentoo.org) but he's not on Bugzilla so I will just forward this to
him.
Grass roots campaign! Get rid of all the silly runtime SIGILL checks for
AltiVec and make package builder's lives easier (maybe this should be a
secondary effort to actually modularizing xorg-x11-libs because that thing is a
monster and rebuilding this one library WITH AltiVec support took an hour..)
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.