Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: "Maciej W. Rozycki" <macro@mips.com>
Cc: 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, 10 Apr 2007 15:44:00 -0000	[thread overview]
Message-ID: <20070410154430.GG10890@caradoc.them.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0703261627260.32723@perivale.mips.com>

On Mon, Mar 26, 2007 at 05:00:01PM +0100, Maciej W. Rozycki wrote:
>  This new patch has been tested natively for mips-unknown-linux-gnu and 
> remotely for mipsisa32-sde-elf, using mips-sim-sde32/-EB and 
> mips-sim-sde32/-EL as the targets.

If you really want to build up some bonus points, you could extend the
argument passing testcases to trigger some of these cases :-)

> 2007-03-26  Maciej W. Rozycki  <macro@mips.com>
>             Nigel Stephens  <nigel@mips.com>
> 
> 	* mips-tdep.c (mips_o32_push_dummy_call): Take account of
> 	argument alignment requirements when calculating stack space
> 	required.  When aligning an arg register to eight bytes
> 	boundary, align stack_offset too.  Write floating-point
> 	arguments to the appropriate integer register if need go there.
> 	(mips_o64_push_dummy_call): Likewise.
> 
>  It looks like the calls to mips_abi_regsize() within are now redundant in 
> these functions, because the result is implied by the very fact of calling 
> either of these functions, but this is functionally independent from this 
> change so I think it should be dealt with separately.

I agree.

>  OK to apply?

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.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-04-10 15:44 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 [this message]
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
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=20070410154430.GG10890@caradoc.them.org \
    --to=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