Re: [Valgrind-users] Need testers for MMX support

[Crispin F. <cr...@th...>]

Hi,

I had a bit of a problem getting it to compile, I got:

make[1]: Entering directory `/space/crispin/valgrind/coregrind'
gcc   -DVG_LIBDIR="\"/opt/valgrind/lib"\"   -Winline -Wall -Wshadow -O
-fomit-frame-pointer -mpreferred-stack-boundary=2 -g -c `test -f
vg_dispatch.S || echo './'`vg_dispatch.S
In file included from vg_dispatch.S:32:
vg_constants.h:35:31: vg_constants_skin.h: No such file or directory
make[1]: *** [vg_dispatch.o] Error 1


so I added $(INCLUDES) into the CFLAGS line in the makefile, not quite
sure what was happening there.

Anyway, I got it compiled, however every program I ran (including 'ls')
aborted with the following error:

Instruction failed sanity check:
           2: CALLML    q0              [abcdSD]
opcode:          54
lit32:           0x0
size:            4
val1,val2,val3:  1, 0, 0
tag1,tag2,tag3:  0, 7, 7
flags_r:         0x0
flags_w:         0x0
extra4b:         0x0
cond:            0x0
signed_widen:    0
jmpkind:         0
argc,regparms_n: 0, 0
has_ret_val:     0
regs_live_after: [abcdSD]

valgrind: vg_translate.c:628 (vgPlain_saneUCodeBlock): Assertion `sane'
failed.


Could that be related to the compile problem?

Crispin



On Wed, 2003-03-26 at 21:30, Julian Seward wrote:
> Greetings, y'all.
> 
> I just committed to the cvs head, initial support for MMX instructions.
> Just MMX, not SSE or SSE2.  SSE and SSE2 are for later; a staged approach
> keeps the resulting code simpler and more maintainable (I hope).
> 
> Most MMX instructions now work.  What would be very useful is for
> people who have apps with MMX instructions, to check out and build the
> head [details below] and then run their MMXish apps on it.  There will 
> be initial breakage, but the sooner this is done, the sooner we will 
> have working MMX support :-)
> 
> So, can anyone help out?
> 
> If this all works out satisfactorily, I will seriously consider backporting
> it to the stable branch (the >= 1.9.4 series).
> 
> J
> 
> 
> Building from anon cvs:
> You need autoconf >= 1.5.  Apart from that it should be easy.
> 
> Here's how:
> 
> cvs -d:pserver:ano...@cv...:/cvsroot/valgrind login
> 
> When prompted for a password for anonymous, simply press the Enter key.
> 
> cvs -z3 -d:pserver:ano...@cv...:/cvsroot/valgrind 
>           co valgrind
> 
> cd valgrind
> ./autogen.sh
> ./configure --prefix=....
> make
> make install
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by:
> The Definitive IT and Networking Event. Be There!
> NetWorld+Interop Las Vegas 2003 -- Register today!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
> _______________________________________________
> Valgrind-users mailing list
> Val...@li...
> https://lists.sourceforge.net/lists/listinfo/valgrind-users