public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj+buildbot@redhat.com
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] S390: Restructure s390_push_dummy_call
Date: Mon, 27 Apr 2015 11:52:00 -0000	[thread overview]
Message-ID: <80f75320167acb66486124c6b03e715596e9c789@kwanyin> (raw)

*** TEST RESULTS FOR COMMIT 80f75320167acb66486124c6b03e715596e9c789 ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: 80f75320167acb66486124c6b03e715596e9c789

S390: Restructure s390_push_dummy_call
Simplify the structure of s390_push_dummy_call and its various helper
functions.  This reduces the code and makes it easier to extend.  The
new code should be functionally equivalent to the old one, except that
copies created by the caller are now always aligned on an 8-byte
boundary.

gdb/ChangeLog:

	* s390-linux-tdep.c
	(is_float_singleton): Remove function.  Move the "singleton" part
	of the logic...
	(s390_effective_inner_type): ...here.  New function.
	(is_float_like): Remove function.  Inline its logic...
	(s390_function_arg_float): ...here.
	(is_pointer_like, is_integer_like, is_struct_like): Remove
	functions.  Inline their logic...
	(s390_function_arg_integer): ...here.
	(s390_function_arg_pass_by_reference): Remove function.
	(extend_simple_arg): Remove function.
	(alignment_of): Remove function.
	(struct s390_arg_state): New structure.
	(s390_handle_arg): New function.
	(s390_push_dummy_call): Move parameter placement logic to the new
	function s390_handle_arg.  Call it for calculating the stack area
	sizes first, and again for actually writing the parameters.


             reply	other threads:[~2015-04-27 11:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-27 11:52 sergiodj+buildbot [this message]
2015-04-27 11:52 ` Failures on Fedora-ppc64be-m64, branch master sergiodj+buildbot
2015-04-27 12:56 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-04-27 13:56 ` Failures on Debian-i686-native-gdbserver, " sergiodj+buildbot
2015-04-27 13:59 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-04-27 14:10 ` Failures on Debian-i686, " sergiodj+buildbot
2015-04-27 14:18 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot
2015-04-27 17:10 ` Failures on Fedora-i686, " sergiodj+buildbot
2015-04-27 17:46 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2015-04-27 17:51 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2015-04-27 18:49 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2015-04-27 19:59 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-04-27 20:08 ` Failures on Fedora-ppc64le-cc-with-index, " sergiodj+buildbot
2015-04-27 20:20 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot
2015-04-27 20:27 ` Failures on Fedora-ppc64le-m64, " sergiodj+buildbot

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=80f75320167acb66486124c6b03e715596e9c789@kwanyin \
    --to=sergiodj+buildbot@redhat.com \
    --cc=gdb-testers@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).