From: Mark Kettenis <kettenis@science.uva.nl>
To: Pierre Muller <pierre@idefix.wisa.be>
Cc: gdb@sourceware.cygnus.com
Subject: Re: [RFC] cygwin GDB "long long" return value error
Date: Thu, 04 Oct 2001 12:08:00 -0000 [thread overview]
Message-ID: <s3ipu836x6i.fsf@soliton.wins.uva.nl> (raw)
In-Reply-To: <3.0.6.32.20011004012430.010f56b0@idefix.wisa.be>
Pierre Muller <pierre@idefix.wisa.be> writes:
> This macro has a correct implementation in config/i386/tm-i386.h
> where 64bit integers are taken from the edx:eax pair.
Nowadays it's a function in i386-tdep.c.
> But config/i386/tm-i386v.h overwrites this macro
> by using memcpy on the register buffer, which then leads to
> using ecx:eax as return value.
Yep. I don't know what the origional System V compiler did, but it's
unlikely that it did return 64-bit quantities in ecx:eax, if it
supported 64-bit quantities at all. I have a patch that removes most
of the presumably unecessary junk from tm-i386v.h. I might as well
post it.
> As cygwin version relies on tm-i386v.h,
> the 64bit integers are wrong.
IMHO cygwin shouldn't include tm-i386v.h. tm-i386.h already the
necessary stuff, and really does a better job at it. Cygwin
defenitely isn't derived from System V.
> Anyhow STORE_RETURN_VALUE in config/i386/tm-i386.h
> suffers from the same error, the "long long" value will be copied
> into ecx:eax instead of edx:eax
Fixed in the current sources (both mainline and the 5.1 branch) :-).
Thanks for the report anyway,
Mark
next prev parent reply other threads:[~2001-10-04 12:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pierre>
[not found] ` <Muller's>
[not found] ` <message>
[not found] ` <of>
[not found] ` <Thu,>
[not found] ` <04>
[not found] ` <Oct>
[not found] ` <2001>
[not found] ` <01:24:30>
[not found] ` <+0200>
2001-10-03 16:17 ` Pierre Muller
2001-10-04 12:08 ` Mark Kettenis [this message]
2001-10-05 3:12 ` [RFC/RFA] fix " Pierre Muller
2001-10-10 19:09 ` Christopher Faylor
2001-10-10 19:50 ` Stan Shebs
2001-10-11 21:33 ` Christopher Faylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=s3ipu836x6i.fsf@soliton.wins.uva.nl \
--to=kettenis@science.uva.nl \
--cc=gdb@sourceware.cygnus.com \
--cc=pierre@idefix.wisa.be \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox