From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: luisgpm@linux.vnet.ibm.com
Cc: Daniel Jacobowitz <drow@false.org>,
Joel Brobecker <brobecker@adacore.com>,
gdb-patches@sourceware.org
Subject: Re: [RFC] Linux-specific ppc32 ABI
Date: Fri, 25 Jan 2008 16:13:00 -0000 [thread overview]
Message-ID: <1201277155.11950.134.camel@localhost.localdomain> (raw)
In-Reply-To: <1200086736.26270.35.camel@gargoyle>
On Fri, 2008-01-11 at 19:25 -0200, Luis Machado wrote:
> > > > How about an extra flag inside the gdbarch_tdep structure that
> > > > you'll be using inside the push dummy call? It would be a shame
> > > > duplicate this function when most of it is common.
<snip>
> Actually, we won't need to go through the flag. I've checked and the
> PPC/Linux ABI conforms with the PPC/SysV ABI regarding Calling Sequences
> and the Stack layout.
<snip>
> The SysV ABI says we should promote exceeding float parameters (the ones
> that should go to the stack) to double, and store then with 8 bytes
> alignment in the stack.
<snip>
> GCC (XLC as well) doesn't promote floats to doubles and does not align
> them to 8 bytes in the stack. Actually, it just aligns the prototyped
> float parameters to 4 bytes in the stack.
>
> This is something that needs to be improved in the ABI text.
>
> The patch follows, with a minor change in the ABI handling for PPC32 and
> a testcase Thiago wrote to verify the problem.
>
> Comments?
Ping?
It would be nice if someone could test this patch in other systems which
use the SysV ppc32 ABI, to see if they actually implement what is in the
ABI specification or if they also do what Linux actually does. If the
former, this patch could go in. If the latter, we could use the
suggested flag in gdbarch_tdep to restrict this fix only to Linux.
--
[]'s
Thiago Jung Bauermann
Software Engineer
IBM Linux Technology Center
next prev parent reply other threads:[~2008-01-25 16:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 19:00 Luis Machado
2008-01-10 19:13 ` Daniel Jacobowitz
2008-01-10 19:26 ` Thiago Jung Bauermann
2008-01-11 6:06 ` Joel Brobecker
2008-01-11 15:55 ` Luis Machado
2008-01-11 15:58 ` Daniel Jacobowitz
2008-01-11 21:26 ` Luis Machado
2008-01-25 16:13 ` Thiago Jung Bauermann [this message]
2008-01-25 16:51 ` Thiago Jung Bauermann
2008-01-26 18:18 ` Mark Kettenis
2008-01-26 19:08 ` Joseph S. Myers
2008-01-26 19:10 ` Mark Kettenis
2008-01-28 20:32 ` Thiago Jung Bauermann
2008-02-01 21:42 ` Thiago Jung Bauermann
2008-02-01 22:39 ` Joel Brobecker
2008-02-02 0:27 ` Mark Kettenis
2008-02-06 3:57 ` Thiago Jung Bauermann
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=1201277155.11950.134.camel@localhost.localdomain \
--to=bauerman@br.ibm.com \
--cc=brobecker@adacore.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=luisgpm@linux.vnet.ibm.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