From: Michael Snyder <Michael.Snyder@access-company.com>
To: "Maciej W. Rozycki" <macro@mips.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: Tue, 17 Apr 2007 20:52:00 -0000 [thread overview]
Message-ID: <1176842694.5381.22.camel@svmsnyderlnx.palmsource.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0704171356050.17222@perivale.mips.com>
On Tue, 2007-04-17 at 15:50 +0100, Maciej W. Rozycki wrote:
> On Tue, 10 Apr 2007, Daniel Jacobowitz wrote:
>
> > If you really want to build up some bonus points, you could extend the
> > argument passing testcases to trigger some of these cases :-)
>
> I think gdb.base/funcargs.exp and gdb.base/varargs.exp should already
> cover the interesting combinations and I would suggest that only if any
> new problem pops up, they should get updated to take it into account.
>
> > Yes, this is OK. I'll just trust you on the underlying ABI issues,
> > since you know it better than I do. It all looks sane.
>
> 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.
next prev parent reply other threads:[~2007-04-17 20:45 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 [this message]
2007-04-18 9:59 ` Maciej W. Rozycki
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=1176842694.5381.22.camel@svmsnyderlnx.palmsource.com \
--to=michael.snyder@access-company.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=macro@linux-mips.org \
--cc=macro@mips.com \
--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