[valgrind] [Bug 353370] RDRAND amd64->IR: unhandled instruction bytes: 0x48 0xF 0xC7 0xF0 0x72 0x4 0xFF 0xC9

[Cyp]

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

--- Comment #29 from Cyp  ---
It is now. And seems to work, thanks.

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 353370] RDRAND amd64->IR: unhandled instruction bytes: 0x48 0xF 0xC7 0xF0 0x72 0x4 0xFF 0xC9

[Tom Hughes]

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

--- Comment #28 from Tom Hughes  ---
That latest change isn't actually committed yet ;-)

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 353370] RDRAND amd64->IR: unhandled instruction bytes: 0x48 0xF 0xC7 0xF0 0x72 0x4 0xFF 0xC9

[Julian Seward]

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

--- Comment #27 from Julian Seward  ---
That doesn't invalidate Tom's comment though: you should always test
with CPUID at run time for the presence of any particular instruction
set extension, before using it.  Especially for recent or obscure
extensions.

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 353370] RDRAND amd64->IR: unhandled instruction bytes: 0x48 0xF 0xC7 0xF0 0x72 0x4 0xFF 0xC9

[Julian Seward]

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

--- Comment #26 from Julian Seward  ---
(In reply to Tom Hughes from comment #25)
> So actually there is a later commit which does actually implement RDRAND but
> only  for AVX2 capable CPUs which yours is not.

I think Mark just fixed it to work on AVX-only capable CPUs too.  See
bug 408009.

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 353370] RDRAND amd64->IR: unhandled instruction bytes: 0x48 0xF 0xC7 0xF0 0x72 0x4 0xFF 0xC9

[Tom Hughes]

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

--- Comment #25 from Tom Hughes  ---
So actually there is a later commit which does actually implement RDRAND but
only  for AVX2 capable CPUs which yours is not. My other point remains correct,
that we won't advertise RDRAND on any machine where we don't support it.

The reason by the way that we only do it for AVX2 capable CPUs is that we only
support a limited set of CPU profiles and the next one down is:

  Intel(R) Core(TM) i5-2300 CPU @ 2.80GHz

which is not RDRAND capable.

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 353370] RDRAND amd64->IR: unhandled instruction bytes: 0x48 0xF 0xC7 0xF0 0x72 0x4 0xFF 0xC9

[Tom Hughes]

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

--- Comment #24 from Tom Hughes  ---
That's badly written - they are not supported but this bug is resolved by
making valgrind's emulation of the cpuid instruction remove the bit which
claims support for them.

So an application which tests for rdrand before using it will now work but one
which just assumes it can use it will still fail.

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 353370] RDRAND amd64->IR: unhandled instruction bytes: 0x48 0xF 0xC7 0xF0 0x72 0x4 0xFF 0xC9

[Cyp]

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

Cyp  changed:

   What|Removed |Added

 CC||cyp...@gmail.com

--- Comment #23 from Cyp  ---
I'm seeing this with valgrind-3.15.0, even though the release notes say RdRand
is now supported.

The system is compiled with -march=native on an “Intel(R) Core(TM) i7-3770K CPU
@ 3.50GHz”.

--

$ valgrind scribus
==26338== Memcheck, a memory error detector
==26338== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==26338== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info
==26338== Command: scribus
==26338== 
vex amd64->IR: unhandled instruction bytes: 0xF 0xC7 0xF0 0xB9 0x1 0x0 0x0 0x0
0x89 0x3
vex amd64->IR:   REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR:   VEX=0 VEX.L=0 VEX.n=0x0 ESC=0F
vex amd64->IR:   PFX.66=0 PFX.F2=0 PFX.F3=0
==26338== valgrind: Unrecognised instruction at address 0x8769603.
==26338==at 0x8769603: _rdrand32_step (immintrin.h:138)
==26338==by 0x8769603: qt_random_cpu (qrandom.cpp:114)
==26338==by 0x8769603: QRandomGenerator::SystemGenerator::generate(unsigned
int*, unsigned int*) (qrandom.cpp:370)
==26338==by 0x87BC11A: fillRange (qrandom.h:143)
==26338==by 0x87BC11A: generate (qrandom.h:87)
==26338==by 0x87BC11A: qt_create_qhash_seed() (qhash.cpp:299)
==26338==by 0x87BC1D4: qt_initialize_qhash_seed (qhash.cpp:325)
==26338==by 0x87BC1D4: qt_initialize_qhash_seed() (qhash.cpp:322)
==26338==by 0x87BC7C9: QHashData::detach_helper(void (*)(QHashData::Node*,
void*), void (*)(QHashData::Node*), int, int) (qhash.cpp:502)
==26338==by 0x87CFDB9: QHash::Node>::detach_helper() [clone .isra.191] (qhash.h:599)
==26338==by 0x87D5FFB: detach (qhash.h:275)
==26338==by 0x87D5FFB: find (qhash.h:901)
==26338==by 0x87D5FFB: take (qcache.h:154)
==26338==by 0x87D5FFB: prepareEngine_helper(QRegExpPrivate*)
(qregexp.cpp:3853)
…

--

http://www.valgrind.org/docs/manual/dist.news.html
Release 3.15.0 (12 April 2019)
* amd64 (x86_64): the RDRAND and F16C insn set extensions are now supported.

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 353370] RDRAND amd64->IR: unhandled instruction bytes: 0x48 0xF 0xC7 0xF0 0x72 0x4 0xFF 0xC9

[Mark Wielaard]

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

Mark Wielaard  changed:

   What|Removed |Added

 CC||for...@prenav.com

--- Comment #22 from Mark Wielaard  ---
*** Bug 401846 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 353370] RDRAND amd64->IR: unhandled instruction bytes: 0x48 0xF 0xC7 0xF0 0x72 0x4 0xFF 0xC9

[Mark Wielaard]

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

Mark Wielaard  changed:

   What|Removed |Added

 CC||sebastian.groth@enervision.
   ||de

--- Comment #21 from Mark Wielaard  ---
*** Bug 400279 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 353370] RDRAND amd64->IR: unhandled instruction bytes: 0x48 0xF 0xC7 0xF0 0x72 0x4 0xFF 0xC9

[Tom Hughes]

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

Tom Hughes  changed:

   What|Removed |Added

 CC||cj-...@zougloub.eu

--- Comment #20 from Tom Hughes  ---
*** Bug 396176 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 353370] RDRAND amd64->IR: unhandled instruction bytes: 0x48 0xF 0xC7 0xF0 0x72 0x4 0xFF 0xC9

[Mark Wielaard]

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

Mark Wielaard  changed:

   What|Removed |Added

 CC||mathias.cabiochdelalande@gm
   ||ail.com

--- Comment #19 from Mark Wielaard  ---
*** Bug 395809 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 353370] RDRAND amd64->IR: unhandled instruction bytes: 0x48 0xF 0xC7 0xF0 0x72 0x4 0xFF 0xC9

[bugzilla_noreply]

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

danilo.borq...@gmail.com changed:

   What|Removed |Added

 CC||danilo.borq...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 353370] RDRAND amd64->IR: unhandled instruction bytes: 0x48 0xF 0xC7 0xF0 0x72 0x4 0xFF 0xC9

[Tom Hughes]

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

Tom Hughes  changed:

   What|Removed |Added

 CC||ezy...@mit.edu

--- Comment #18 from Tom Hughes  ---
*** Bug 387940 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 353370] RDRAND amd64->IR: unhandled instruction bytes: 0x48 0xF 0xC7 0xF0 0x72 0x4 0xFF 0xC9

[Mark Wielaard]

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

Mark Wielaard  changed:

   What|Removed |Added

 CC||gcc.h...@gmail.com

--- Comment #17 from Mark Wielaard  ---
*** Bug 381699 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 353370] RDRAND amd64->IR: unhandled instruction bytes: 0x48 0xF 0xC7 0xF0 0x72 0x4 0xFF 0xC9

[Tom Hughes]

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

Tom Hughes  changed:

   What|Removed |Added

 CC||juliusde...@gmail.com

--- Comment #16 from Tom Hughes  ---
*** Bug 378180 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 353370] RDRAND amd64->IR: unhandled instruction bytes: 0x48 0xF 0xC7 0xF0 0x72 0x4 0xFF 0xC9

[Tom Hughes]

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

Tom Hughes  changed:

   What|Removed |Added

 CC||cochamb...@tycoint.com

--- Comment #15 from Tom Hughes  ---
*** Bug 375845 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 353370] RDRAND amd64->IR: unhandled instruction bytes: 0x48 0xF 0xC7 0xF0 0x72 0x4 0xFF 0xC9

[Julian Seward via KDE Bugzilla]

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

Julian Seward  changed:

   What|Removed |Added

 CC||k...@kinomoto.me

--- Comment #14 from Julian Seward  ---
*** Bug 365325 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 353370] RDRAND amd64->IR: unhandled instruction bytes: 0x48 0xF 0xC7 0xF0 0x72 0x4 0xFF 0xC9

[Tom Hughes via KDE Bugzilla]

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

Tom Hughes  changed:

   What|Removed |Added

 CC||brat...@opera.com

--- Comment #13 from Tom Hughes  ---
*** Bug 358988 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 353370] RDRAND amd64->IR: unhandled instruction bytes: 0x48 0xF 0xC7 0xF0 0x72 0x4 0xFF 0xC9

[Mark Wielaard via KDE Bugzilla]

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

Mark Wielaard  changed:

   What|Removed |Added

 CC||miabr...@gmail.com

--- Comment #12 from Mark Wielaard  ---
*** Bug 357873 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.