Floating point failures on x64
yebblies at nospamgmail.com
Fri Feb 24 03:20:42 PST 2012
Do you know what happened to the rest of the intel disassembly? It ends
I'd use the other listing but the callq instructions seem to be displaying
the return address instead of the target address.
"Martin Nowak" <dawg at dawgfoto.de> wrote in message
news:op.v96domsnsqugbd at dawg-freebsd.lan...
> On Fri, 24 Feb 2012 09:02:05 +0100, Daniel Murphy
> <yebblies at nospamgmail.com> wrote:
>> Thanks heaps! Only failing for cfloat+ now!
>> I've updated the pull, do you mind doing it again?
>> "Martin Nowak" <dawg at dawgfoto.de> wrote in message
>> news:op.v958yuyvsqugbd at dawg-freebsd.lan...
>>> On Fri, 24 Feb 2012 06:57:22 +0100, Daniel Murphy
>>> <yebblies at nospamgmail.com> wrote:
>>>> I've been trying to fix issue 4155, but it's a little difficult without
>>>> ability to test on x64 (I'm on win32). Could anybody compile the
>>>> code for me with 'dmd -m64' with this patch
>>>> https://github.com/D-Programming-Language/dmd/pull/760 and send me the
>>> http://codepad.org/1w2jRctt - objconv
>>> http://codepad.org/pOCsPsMi - objdump (doesn't know sahf)
> Intel or AT&T?
> http://codepad.org/4Gr237NH - dmd -c bug2.d && objconv -fasm bug2.o
> http://codepad.org/MhqFv8ik - dmd -c bug2.d && objdump -d bug2.o
More information about the Digitalmars-d