From: "Maciej W. Rozycki" <macro@mips.com>
To: Michael Snyder <Michael.Snyder@access-company.com>
Cc: Daniel Jacobowitz <drow@false.org>,
Mark Kettenis <mark.kettenis@xs4all.nl>,
gdb-patches@sourceware.org, Nigel Stephens <nigel@mips.com>,
"Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: mips-tdep.c: FP varargs fixes
Date: Wed, 18 Apr 2007 09:59:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.61.0704180924420.28492@perivale.mips.com> (raw)
In-Reply-To: <1176842694.5381.22.camel@svmsnyderlnx.palmsource.com>
On Tue, 17 Apr 2007, Michael Snyder wrote:
> > Well, GCC is the definite reference in this case ...
>
> You would think so -- but GCC has been known to get it wrong.
> Historically, when gcc differs from the MIPS spec, we go with
> the MIPS spec. Even if it means our tests fail.
No question about it, but it makes sense only if accompanied with the
respective bug report against GCC. Then some areas of the MIPS o32 ABI
are obscure enough or plainly wrong (= useless as is -- see e.g. the
R_MIPS_PC16 relocation), so that using a live piece of software instead is
reasonably enough. And o64 does not even exist. ;-)
Maciej
next prev parent reply other threads:[~2007-04-18 8:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-23 14:41 Maciej W. Rozycki
2007-03-23 14:51 ` Mark Kettenis
2007-03-26 16:00 ` Maciej W. Rozycki
2007-04-10 15:44 ` Daniel Jacobowitz
2007-04-17 14:56 ` Maciej W. Rozycki
2007-04-17 15:00 ` Daniel Jacobowitz
2007-04-17 16:05 ` Maciej W. Rozycki
2007-04-17 16:26 ` Daniel Jacobowitz
2007-04-17 20:52 ` Michael Snyder
2007-04-18 9:59 ` Maciej W. Rozycki [this message]
2007-03-23 14:53 ` Andreas Schwab
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=Pine.LNX.4.61.0704180924420.28492@perivale.mips.com \
--to=macro@mips.com \
--cc=Michael.Snyder@access-company.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=macro@linux-mips.org \
--cc=mark.kettenis@xs4all.nl \
--cc=nigel@mips.com \
/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