Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: drow@false.org, janani@linux.ibm.com, gdb-patches@sourceware.org,
		pgilliam@us.ibm.com, janani@us.ibm.com
Subject: Re: [patch] Pushing Inferior Function Arguments onto Stack on  	PowerPC64 machines
Date: Wed, 04 Oct 2006 20:27:00 -0000	[thread overview]
Message-ID: <je4pujaksj.fsf@sykes.suse.de> (raw)
In-Reply-To: <200610042018.k94KIbLQ007549@elgar.sibelius.xs4all.nl> (Mark 	Kettenis's message of "Wed, 4 Oct 2006 22:18:37 +0200 (CEST)")

Mark Kettenis <mark.kettenis@xs4all.nl> writes:

> Indeed.  GCC has been getting things wrong in this area before.  And
> on top of that, some versions of GCC get it right while other versions
> get it wrong.  If there are indeed versions of GCC in widespread use
> that do not follow the ABI, we should probably try to add a workaround
> in GCC.  But if there are also versions of GCC that do follow the ABI,
> adding such a workaround might be impossible.

AFAICS, GCC on AIX follows the ABI here, but ppc64-linux deviates from it.
This is controlled by AGGREGATES_PAD_UPWARD_ALWAYS in
rs6000.c:function_arg_padding in the gcc source.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."


  reply	other threads:[~2006-10-04 20:27 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-04 19:00 janani
2006-10-04 19:11 ` Daniel Jacobowitz
2006-10-04 19:14   ` Daniel Jacobowitz
2006-10-04 20:19   ` Mark Kettenis
2006-10-04 20:27     ` Andreas Schwab [this message]
     [not found]   ` <OFE88464A1.C58B072A-ON872571FD.006ABA69-862571FD.006C7CFB@us.ibm.com>
2006-10-04 20:26     ` Daniel Jacobowitz
  -- strict thread matches above, loose matches on Subject: below --
2006-10-04 21:02 janani
     [not found] <20041026075115.4A2C354AAB5@stray.canids>
     [not found] ` <20041026132924.GA26886@nevyn.them.org>
     [not found]   ` <drow@false.org>
2004-10-26 15:01     ` backtrace changes current source location Felix Lee
2004-10-27 17:35       ` Andrew Cagney
2004-10-27 17:40         ` Daniel Jacobowitz
2004-10-28  0:52         ` Felix Lee
2004-10-29 15:22           ` Andrew Cagney
2004-10-29 15:36             ` Daniel Jacobowitz
2004-10-29 22:07             ` Felix Lee
2004-10-30  0:02               ` Andrew Cagney
2004-10-30  3:28                 ` Felix Lee
2004-11-01  4:38                   ` Felix Lee
2004-11-01 16:04                     ` Andrew Cagney
2004-11-01 16:13                     ` Daniel Jacobowitz
2004-11-05  8:51     ` Felix Lee
2006-10-04 20:43     ` [patch] Pushing Inferior Function Arguments onto Stack on PowerPC64 machines David Edelsohn
2006-10-04 20:52       ` Daniel Jacobowitz
2006-10-04 19:54 janani
2006-10-03 19:15 Janani Janakiraman
2006-10-03 19:20 ` Daniel Jacobowitz
2005-08-15 13:37 Procedure for large drop? Paul Hilfinger
2005-08-15 14:15 ` Daniel Jacobowitz
2005-08-15 21:50   ` Paul Hilfinger
2005-08-16  2:36     ` Jason Molenda
2005-08-20 22:15   ` Paul Hilfinger
2005-08-22 19:00     ` Daniel Jacobowitz

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=je4pujaksj.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=janani@linux.ibm.com \
    --cc=janani@us.ibm.com \
    --cc=mark.kettenis@xs4all.nl \
    --cc=pgilliam@us.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