-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi, and thanks everybody for the help so far;
I uploaded mplayer 1.0~rc1-16 ; it was built on the alpha buildd with
the '-mcpu=ev5' option.
If somebody has a CPU without MVI, may please s/he test if s/he can play
a mpeg file such as
Hello,
On Sun, Aug 26, 2007 at 04:15:27PM -0700, Steve Langasek wrote:
On Sun, Aug 26, 2007 at 09:12:27PM +0200, A Mennucc wrote:
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
This is all correct, but again, the mplayer code explicitly checks the
cputype at runtime and dyanmically uses the most efficient code.
So, it should be possible to build for all systems (ev5) and yet
maintain the performance of MVI for systems that support it.
...tom
Helge Kreutzmann
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi Steve and all,
I am currently tryin to figure out what I should set in '-mcpu' : is it
DEB_HOST_GNU_CPU ?
And, just for the record...
Steve Langasek ha scritto:
On Sun, Aug 26, 2007 at 09:12:27PM +0200, A Mennucc wrote:
So for starters,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi
I prepared a patch that may solve the problem ; but unfortunately I
cannot test it, since I do not have access to alpha machines.
The source is
http://tonelli.sns.it/pub/mplayer/sid/mplayer_1.0~rc1-16.dsc
Again, I looked at the code, there should be no reason do disable MVI -
the code already checks the CPU type and runs the appropriate code for
those accelerated instructions.
You should be able to keep ALPHA_CAN_BUILD_MVI, but just pull down the
cpu type to ev5, or alternatively, keep the
On Mon, Aug 27, 2007 at 12:33:44PM +0200, A Mennucc wrote:
I am currently tryin to figure out what I should set in '-mcpu' : is it
DEB_HOST_GNU_CPU ?
Er, preferably nothing at all. There's no good reason to be overriding
gcc's default optimization here; your package should be targetting the
-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 abilities
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
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
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
11 matches
Mail list logo
