From: Jeff Law <law@redhat.com>
To: gcc-patches@gcc.gnu.org, richard.sandiford@arm.com
Subject: Re: [01/13] Add pass_va_arg_by_reference
Date: Mon, 19 Aug 2019 20:04:00 -0000 [thread overview]
Message-ID: <ded2b4be-8a68-24b7-6ec8-3e32df0c6899@redhat.com> (raw)
In-Reply-To: <mptwof9chq8.fsf@arm.com>
On 8/19/19 9:11 AM, Richard Sandiford wrote:
> This patch splits out a common idiom from the va_arg gimplification
> routines, so that there's only one place to update later.
>
>
> 2019-08-19 Richard Sandiford <richard.sandiford@arm.com>
>
> gcc/
> * calls.h (pass_va_arg_by_reference): Declare.
> * calls.c (pass_va_arg_by_reference): New function.
> * config/aarch64/aarch64.c (aarch64_gimplify_va_arg_expr): Use it.
> * config/alpha/alpha.c (alpha_gimplify_va_arg): Likewise.
> * config/gcn/gcn.c (gcn_gimplify_va_arg_expr): Likewise.
> * config/i386/i386.c (ix86_gimplify_va_arg): Likewise.
> * config/ia64/ia64.c (ia64_gimplify_va_arg): Likewise.
> * config/mips/mips.c (mips_std_gimplify_va_arg_expr): Likewise.
> (mips_gimplify_va_arg_expr): Likewise.
> * config/msp430/msp430.c (msp430_gimplify_va_arg_expr): Likewise.
> * config/pa/pa.c (hppa_gimplify_va_arg_expr): Likewise.
> * config/rs6000/rs6000-call.c (rs6000_gimplify_va_arg): Likewise.
> * config/s390/s390.c (s390_gimplify_va_arg): Likewise.
> * config/sparc/sparc.c (sparc_gimplify_va_arg): Likewise.
> * config/spu/spu.c (spu_gimplify_va_arg_expr): Likewise.
> * config/tilegx/tilegx.c (tilegx_gimplify_va_arg_expr): Likewise.
> * config/tilepro/tilepro.c (tilepro_gimplify_va_arg_expr): Likewise.
> * config/visium/visium.c (visium_gimplify_va_arg): Likewise.
> * config/xtensa/xtensa.c (xtensa_gimplify_va_arg_expr): Likewise.
> * targhooks.c (std_gimplify_va_arg_expr): Likewise.
OK
jeff
next prev parent reply other threads:[~2019-08-19 19:50 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 15:15 [00/13] Pass an argument descriptor to target hooks Richard Sandiford
2019-08-19 15:16 ` [01/13] Add pass_va_arg_by_reference Richard Sandiford
2019-08-19 20:04 ` Jeff Law [this message]
2019-08-19 15:17 ` [02/13] Add must_pass_va_arg_in_stack Richard Sandiford
2019-08-19 20:05 ` Jeff Law
2019-08-19 15:18 ` [03/13] Use function_arg_info for TARGET_ARG_PARTIAL_BYTES Richard Sandiford
2019-08-19 20:42 ` Jeff Law
2019-08-19 15:19 ` [04/13] Use function_arg_info for TARGET_PASS_BY_REFERENCE Richard Sandiford
2019-08-19 20:43 ` Jeff Law
2019-08-19 15:20 ` [05/13] Use function_arg_info for TARGET_SETUP_INCOMING_ARGS Richard Sandiford
2019-08-19 20:50 ` Jeff Law
2019-08-19 15:21 ` [06/13] Use function_arg_info for TARGET_FUNCTION_(INCOMING_)ARG Richard Sandiford
2019-08-19 21:07 ` Jeff Law
2019-08-19 15:22 ` [07/13] Use function_arg_info for TARGET_FUNCTION_ARG_ADVANCE Richard Sandiford
2019-08-19 21:11 ` Jeff Law
2019-08-19 15:23 ` [08/13] Use function_arg_info for TARGET_CALLEE_COPIES Richard Sandiford
2019-08-19 21:16 ` Jeff Law
2019-08-19 15:24 ` [09/13] Use function_arg_info for TARGET_MUST_PASS_IN_STACK Richard Sandiford
2019-08-19 22:04 ` Jeff Law
2019-08-19 15:47 ` [10/13] Add a apply_pass_by_reference_rules helper Richard Sandiford
2019-08-19 22:19 ` Jeff Law
2019-08-19 15:51 ` [11/13] Make function.c use function_arg_info internally Richard Sandiford
2019-08-19 22:47 ` Jeff Law
2019-08-19 15:52 ` [12/13] Make calls.c " Richard Sandiford
2019-08-19 22:49 ` Jeff Law
2019-08-19 15:52 ` [13/13] Add a pass_by_reference flag to function_arg_info Richard Sandiford
2019-08-19 22:54 ` Jeff Law
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=ded2b4be-8a68-24b7-6ec8-3e32df0c6899@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.sandiford@arm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).