-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi
a bug
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=431139
was posted against mplayer sometime ago: it seems that the binary
contains a "itoft" instruction , and this is illegal on some older
alpha CPUs
what should I do ? add a specific-mc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi
I add another info
By looking in
http://buildd.debian.org/fetch.cgi?pkg=mplayer;ver=1.0%7Erc1-15;arch=alpha;stamp=1185972985
I deduced that indeed "configure" detects the CPU of the buildd , as follows
> Checking for GCC & CPU optimization abiliti
Alternatively the code could have checks for the appropriate features by
using the amask instruction and chose the correct code sequences -
probably a win in the MVI cases, unclear about the itoft cases.
It would have to be looked at to see what code path tricks could be played.
Is this code i
On Sun, Aug 26, 2007 at 09:12:27PM +0200, A Mennucc wrote:
> I add another info
> By looking in
> http://buildd.debian.org/fetch.cgi?pkg=mplayer;ver=1.0%7Erc1-15;arch=alpha;stamp=1185972985
> I deduced that indeed "configure" detects the CPU of the buildd , as follows
> > Checking for GCC & CPU o
Turns out it was simple to find the code in question.
The code already checks the amask bits for MVI availability with
CAN_COMPILE_ALPHA_MVI .
So, there should be a way to keep CAN_COMPILE_ALPHA_MVI set but keep the
rest of the program from using ev67 specific instructions - the mvi
acceler
5 matches
Mail list logo