[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [valgrind] [Bug 332917] Valgrind should warn the user that SSE4 is not supported in the 32-bit mode
From:       Timur Iskhodzhanov <timurrrr () google ! com>
Date:       2014-04-02 9:04:48
Message-ID: bug-332917-17878-j4wwNge69w () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=332917

Timur Iskhodzhanov <timurrrr@google.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |eugeni.stepanov@gmail.com,
                   |                            |glider@google.com

--- Comment #2 from Timur Iskhodzhanov <timurrrr@google.com> ---
I like the idea of adding a FAQ link into the message.

Another related idea:
Whenever Valgrind says something like
  vex x86->IR: unhandled instruction bytes: 0x66 0xF 0x38 0x20
I do
-------------------
$ cat >foo.c
void foo() {
asm(".byte 0x66, 0xf, 0x38, 0x20, 0x0");
}
^D

$ gcc -c -O2 foo.c && objdump -d foo.o
66 0f 38 20 00       pmovsxbw (%rax),%xmm0
-------------------
/* Please note Valgrind only prints out the first 4 bytes of the unhandled
instruction, looks like this number should be raised to the maximum instruction
length? */

I wonder if it's possible to automatically invoke something like objdump when
an unhandled instruction happens?
Then Valgrind can just say "hey, pmovsxbw is not handled, sorry".
Otherwise, the FAQ entry should mention the above method.

[adding my colleagues who fought similar problems before]

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]