* PING: [PATCH] i386: Don't generate alias for function return thunk
@ 2018-03-05 12:18 H.J. Lu
0 siblings, 0 replies; only message in thread
From: H.J. Lu @ 2018-03-05 12:18 UTC (permalink / raw)
To: GCC Patches; +Cc: Jan Hubicka
On Mon, Feb 26, 2018 at 12:48 PM, H.J. Lu <hongjiu.lu@intel.com> wrote:
> Function return thunks shouldn't be aliased to indirect branch thunks
> since indirect branch thunks are placed in COMDAT section and a COMDAT
> section with indirect branch may not have function return thunk. This
> patch generates function return thunks directly.
>
> Tested on i686 and x86-64. OK for trunk?
>
> H.J.
> ---
> gcc/
>
> PR target/84574
> * config/i386/i386.c (indirect_thunk_needed): Update comments.
> (indirect_thunk_bnd_needed): Likewise.
> (indirect_thunks_used): Likewise.
> (indirect_thunks_bnd_used): Likewise.
> (indirect_return_needed): New.
> (indirect_return_bnd_needed): Likewise.
> (output_indirect_thunk_function): Add a bool argument for
> function return.
> (output_indirect_thunk_function): Don't generate alias for
> function return thunk.
> (ix86_code_end): Call output_indirect_thunk_function to generate
> function return thunks.
> (ix86_output_function_return): Set indirect_return_bnd_needed
> and indirect_return_needed instead of indirect_thunk_bnd_needed
> and indirect_thunk_needed.
>
> gcc/testsuite/
>
> PR target/84574
> * gcc.target/i386/ret-thunk-9.c: Expect __x86_return_thunk
> label instead of __x86_indirect_thunk label.
PING:
https://gcc.gnu.org/ml/gcc-patches/2018-02/msg01460.html
--
H.J.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2018-03-05 12:18 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-03-05 12:18 PING: [PATCH] i386: Don't generate alias for function return thunk H.J. Lu
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).