On 24.01.2012 01:39, Tom Hughes wrote:
> So you are just seeing the lack of AVX support.
phew kind of relieved, i thought my compiler is playing tricks on me :)
--
Mierswa, Daniel
If you still don't like it, that's ok: that's why I'm boss. I simply know
better than you do.
--- L
On 23/01/12 21:31, Daniel Mierswa wrote:
> On 23.01.2012 22:16, Tom Hughes wrote:
>> Well that is an AVX instruction, but I thought they were only valid in 64
>> bit mode as 0xC5 is (as John said) LDS in 32 bit mode. In 64 bit mode it is
>> a VEX prefix for an AVX instruction.
> Ok interesting.
On 23.01.2012 22:59, John Reiser wrote:
> Probably there is an unexpected interaction between the code in glibc
> which does processor detection using CPUID (etc.), and the code in
> valgrind which delivers "synthetic" results for CPUID. Both valgrind
> and glibc might need to be more robust.
I ju
On 01/23/2012 01:02 PM, Daniel Mierswa wrote:
> On 23.01.2012 21:46, John Reiser wrote:
>> and then perhaps do some matching on the low 12 bits (0xFFF) of the address:
>> 0x44143D0 ==> any address ending in 0x3D0.
>0x000143d0 <+880>: vmovd 0x4(%eax),%xmm0
>> In 32-bit mode, hardware opcode 0x
On 23.01.2012 22:16, Tom Hughes wrote:
> Well that is an AVX instruction, but I thought they were only valid in 64 bit
> mode as 0xC5 is (as John said) LDS in 32 bit mode. In 64 bit mode it is a VEX
> prefix for an AVX instruction.
Ok interesting. Does that mean my gcc produces bad code or is you
On 23/01/12 21:02, Daniel Mierswa wrote:
> On 23.01.2012 21:46, John Reiser wrote:
>> and then perhaps do some matching on the low 12 bits (0xFFF) of the address:
>> 0x44143D0 ==> any address ending in 0x3D0.
> 0x000143d0<+880>: vmovd 0x4(%eax),%xmm0
Well that is an AVX instruction, but I th
On 23.01.2012 21:46, John Reiser wrote:
> and then perhaps do some matching on the low 12 bits (0xFFF) of the address:
> 0x44143D0 ==> any address ending in 0x3D0.
0x000143d0 <+880>: vmovd 0x4(%eax),%xmm0
> In 32-bit mode, hardware opcode 0xC5 is 'LDS' (Load Data Segment register),
> which c
> whenever i want to memcheck a 32bit program on my 64bit system i receive the
> following
> message:
>
> vex x86->IR: unhandled instruction bytes: 0xC5 0xF9 0x6E 0x40
> ==16815== valgrind: Unrecognised instruction at address 0x44143d0.
> ==16815==at 0x44143D0: _dl_sysdep_start (dl-sysdep.c:1
