Re: [Valgrind-developers] Nvidia noticed

[Jeremy F. <je...@go...>]

On Mon, 2003-03-31 at 22:59, Jeremy Fitzhardinge wrote:
> I just installed the new Nvidia drivers on my machine.  I noticed this
> in the release notes:
> 
>         DISABLING CPU SPECIFIC FEATURES
>         
>         Setting the environment variable __GL_FORCE_GENERIC_CPU to a
>         non-zero value will inhibit the use of CPU specific features
>         such as MMX, SSE, or 3DNOW!.  Use of this option may result in
>         performance loss.  This option may be useful in conjunction with
>         software such as the Valgrind memory debugger.

Not that it actually works...

$ __GL_FORCE_GENERIC_CPU=yes valgrind '--skin=none' ./teapot
==4092== Nulgrind, a binary JIT-compiler for x86-linux.
==4092== Copyright (C) 2002, and GNU GPL'd, by Nicholas Nethercote.
==4092== Using valgrind-1.9.4, a program instrumentation system for x86-linux.
==4092== Copyright (C) 2000-2002, and GNU GPL'd, by Julian Seward.
==4092== Estimated CPU clock rate is 1824 MHz
==4092== For more details, rerun with: -v
==4092==
Teapot V1.2
Written by David Bucciarelli (tec...@pl...)
disInstr: unhandled 2-byte opcode: 0x10 0x2 0xF
This _might_ be the result of executing a SSE, SSE2 or 3DNow!
instruction.  Valgrind does not currently support such instructions.  Sorry.
illegal instruction
exit status sigill

	J