From: Daniel Jacobowitz <drow@false.org>
To: "Maciej W. Rozycki" <macro@mips.com>
Cc: gdb-patches@sourceware.org, David Ung <davidu@mips.com>,
"Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: mips-tdep.c: Sign-extend pointers for n32
Date: Wed, 19 Dec 2007 15:28:00 -0000 [thread overview]
Message-ID: <20071219152826.GA30488@caradoc.them.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0712181902330.23732@perivale.mips.com>
On Wed, Dec 19, 2007 at 03:20:20PM +0000, Maciej W. Rozycki wrote:
> You are quite right here -- I have checked the N32 ABI document and it
> says:
>
> "32-bit integer (int) parameters are always sign-extended when passed in
> registers, whether of signed or unsigned type. [This issue does not arise
> in the o32-bit ABI.]"
What happens to an 8-bit unsigned char? How about an 8-bit signed
char?
> I have regression-tested the following rewrite of the original patch
> using the mipsisa32-sde-elf target, with the mips-sim-sde64/-mips64/-EB
> and mips-sim-sde64/-mips64/-EL boards, with the results the same as the
> original.
What ABI is that? I thought none of the ELF targets used n32 or n64,
but maybe SDE is an exception.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-12-19 15:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 14:43 Maciej W. Rozycki
2007-12-16 18:49 ` Daniel Jacobowitz
2007-12-19 15:27 ` Maciej W. Rozycki
2007-12-19 15:28 ` Daniel Jacobowitz [this message]
2007-12-19 16:16 ` Maciej W. Rozycki
2007-12-19 17:08 ` Daniel Jacobowitz
2007-12-20 16:41 ` Maciej W. Rozycki
2007-12-20 17:07 ` Daniel Jacobowitz
2007-12-20 17:18 ` Maciej W. Rozycki
2007-12-20 19:37 ` Daniel Jacobowitz
2007-12-21 4:36 ` Joel Brobecker
2007-12-21 11:34 ` Maciej W. Rozycki
2007-12-21 11:51 ` Joel Brobecker
2007-12-21 12:02 ` Maciej W. Rozycki
2007-12-22 5:30 ` Joel Brobecker
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=20071219152826.GA30488@caradoc.them.org \
--to=drow@false.org \
--cc=davidu@mips.com \
--cc=gdb-patches@sourceware.org \
--cc=macro@linux-mips.org \
--cc=macro@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