Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: joseph@codesourcery.com
Cc: bauerman@br.ibm.com, luisgpm@linux.vnet.ibm.com, drow@false.org,
	        brobecker@adacore.com, gdb-patches@sourceware.org
Subject: Re: [RFC] Linux-specific ppc32 ABI
Date: Sat, 26 Jan 2008 19:10:00 -0000	[thread overview]
Message-ID: <200801261901.m0QJ10Tk010787@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <Pine.LNX.4.64.0801261802500.14186@digraph.polyomino.org.uk> 	(joseph@codesourcery.com)

> Date: Sat, 26 Jan 2008 18:18:17 +0000 (UTC)
> From: "Joseph S. Myers" <joseph@codesourcery.com>
> 
> On Sat, 26 Jan 2008, Mark Kettenis wrote:
> 
> > > > 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.
> > 
> > So both compilers are buggy.
> 
> They would be buggy if they were targetting PowerPC Solaris from 1995 and 
> if the 1995 ABI from Sun is an accurate description of the ABI on that 
> system in the first place.  They are not targetting that OS, they are 
> targetting OSes where the 1995 document is only indicative guidance to a 
> predecessor of the ABIs in use on those OSes.

Well, I'd be surprised if this particular deviation from the 1995
document (which is pretty much a corner case) was a deliberate
deviation.  I'm not suggesting the bug should be fixed though, so I
guess I should have called it a feature ;)

> > > > This is something that needs to be improved in the ABI text.
> > 
> > Well, I suppose you can change it, but I wouldn't call it an
> > improvement.  Who controls the 32-bit PowerPC SystemV ABI these days?
> 
> The Power.org ABI working group, which is working on producing a 
> copyright-clean document (so not using any of the Sun text), copyrights to 
> be assigned to the Linux Foundation, describing the ABIs (both hard and 
> soft float, and E500 and Altivec extensions) as they are in use today for 
> both GNU/Linux and bare-metal (EABI) targets (GNU/Linux and EABI differ in 
> the default for -maix-struct-return, and in the default size of long 
> double, but are otherwise the same at the function-call level).

Thanks for the clarification.


  reply	other threads:[~2008-01-26 19:09 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
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 [this message]
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=200801261901.m0QJ10Tk010787@brahms.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=bauerman@br.ibm.com \
    --cc=brobecker@adacore.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=joseph@codesourcery.com \
    --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