[Issue 11788] [x86] Valgrind unhandled instruction bytes: 0xC8 0x8 0x0 0x0

[d-bugmail at puremagic.com]

https://d.puremagic.com/issues/show_bug.cgi?id=11788



--- Comment #2 from Bruno Deligny <bruno.deligny at gmail.com> 2013-12-21 09:19:48 PST ---
I know but it's already reported on valgrind bugtracker since a while:
https://bugs.kde.org/show_bug.cgi?id=272971
https://bugs.kde.org/show_bug.cgi?id=253433
https://bugs.kde.org/show_bug.cgi?id=317208
I tried with last Valgrind release and with Valgrind svn code.


Nobody seams to care because nobody uses this instruction (enter).

>From Intel's Optimisation Reference Manual:
"Assembler/Compiler Coding Rule 40. (ML impact, M generality) Avoid using
complex instructions (for example, enter, leave, or loop) that have more than 4
uops and require multiple cycles to decode. Use sequences of simple
instructions instead.

Complex instructions may save architectural registers, but incur a penalty of 4
uops to set up parameters for the microcode ROM."


Maybe it would be wise for dmd to be more "standard" (do like gcc or llvm)
because good tool support is extremely important and Valgrind is a leader in
that domain.

-- 
Configure issuemail: https://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------