From: Segher Boessenkool <segher@kernel.crashing.org>
To: "Kewen.Lin" <linkw@linux.ibm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
David Edelsohn <dje.gcc@gmail.com>, AlanM <amodra@gmail.com>
Subject: Re: [PATCH v4] rs6000: Rework ELFv2 support for -fpatchable-function-entry* [PR99888]
Date: Wed, 28 Sep 2022 10:22:24 -0500 [thread overview]
Message-ID: <20220928152224.GS25951@gate.crashing.org> (raw)
In-Reply-To: <c2778c95-439c-ac11-8335-f791ce92be25@linux.ibm.com>
Hi!
On Thu, Aug 25, 2022 at 01:50:28PM +0800, Kewen.Lin wrote:
> --- a/gcc/config/rs6000/rs6000-internal.h
> +++ b/gcc/config/rs6000/rs6000-internal.h
> @@ -183,10 +183,15 @@ extern tree rs6000_fold_builtin (tree fndecl ATTRIBUTE_UNUSED,
> tree *args ATTRIBUTE_UNUSED,
> bool ignore ATTRIBUTE_UNUSED);
>
> +extern void rs6000_print_patchable_function_entry (FILE *,
> + unsigned HOST_WIDE_INT,
> + bool);
> +
> extern bool rs6000_passes_float;
> extern bool rs6000_passes_long_double;
> extern bool rs6000_passes_vector;
> extern bool rs6000_returns_struct;
> extern bool cpu_builtin_p;
>
> +
> #endif
No new random empty lines please.
> + point would be 2, 6 and 14. It's possible to support those
> + other counts of nops by not making a local entry point, but
> + we don't have clear user cases for them, so leave them
"use cases"
> --- a/gcc/doc/invoke.texi
> +++ b/gcc/doc/invoke.texi
> @@ -16717,9 +16717,13 @@ the area size or to remove it completely on a single function.
> If @code{N=0}, no pad location is recorded.
>
> The NOP instructions are inserted at---and maybe before, depending on
> -@var{M}---the function entry address, even before the prologue.
> +@var{M}---the function entry address, even before the prologue. On
> +PowerPC with the ELFv2 ABI, for one function with dual entry points,
> +the local entry point is taken as the function entry for generation.
I think "the local entry point is this function entry address" is a bit
clearer.
> -The maximum value of @var{N} and @var{M} is 65535.
> +The maximum value of @var{N} and @var{M} is 65535. On PowerPC with the
> +ELFv2 ABI, for one function with dual entry points, the supported values
> +for @var{M} are 0, 2, 6 and 14.
"for a function"
Okay for trunk with those trivial chnges. Thanks!
Segher
next prev parent reply other threads:[~2022-09-28 15:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 5:50 Kewen.Lin
2022-09-28 5:37 ` PING^1 " Kewen.Lin
2022-09-28 15:22 ` Segher Boessenkool [this message]
2022-09-30 12:38 ` Kewen.Lin
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=20220928152224.GS25951@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=amodra@gmail.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=linkw@linux.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).