Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [patch]: fix argument passing on S/390 and S/390x
Date: Tue, 01 Jul 2003 00:14:00 -0000	[thread overview]
Message-ID: <vt23chr2jei.fsf@zenia.home> (raw)
In-Reply-To: <vt27k732jrd.fsf@zenia.home>


I've committed this to the 6.0 release branch, too.

Jim Blandy <jimb@redhat.com> writes:

> This is a patch that was discussed and approved long ago; only
> recently has the legal paperwork finally come through.
> 
> 2003-06-30  Jim Blandy  <jimb@redhat.com>
> 
> 	Patch from IBM (authors unspecified, probably Ulrich Weigand and
> 	Gerhard Tonn) for argument passing on the S/390 and S/390x:
> 	* s390-tdep.c (S390_STACK_FRAME_OVERHEAD): This is always space
> 	for 16 registers, and then 32 more bytes.
> 	(S390_STACK_PARAMETER_ALIGNMENT, S390_NUM_FP_PARAMETER_REGISTERS):
> 	New macros.
> 	(is_double_arg): The s390x doesn't handle DOUBLE_ARGS specially.
> 	Move up in the file, since it's now used by is_simple_arg.
> 	(is_simple_arg): Don't assume registers are four bytes long.
> 	Exclude all double arguments.  Extended floats are not simple
> 	args.
> 	(is_power_of_two): New function.
> 	(pass_by_copy_ref): Call is_power_of_two, and check that the
> 	length fits in a register, rather than listing all the acceptable
> 	sizes.  Extended floats are not passed by reference.
> 	(s390_push_arguments): Don't assume registers are four bytes long.
> 	Reserve an argument register to point to the buffer for structures
> 	returned by value.  Use S390_NUM_FP_PARAMETER_REGISTERS and
> 	S390_STACK_FRAME_OVERHEAD.


      reply	other threads:[~2003-07-01  0:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-01  0:06 Jim Blandy
2003-07-01  0:14 ` Jim Blandy [this message]

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=vt23chr2jei.fsf@zenia.home \
    --to=jimb@redhat.com \
    --cc=gdb-patches@sources.redhat.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