From: HAO CHEN GUI <guihaoc@linux.ibm.com>
To: gcc-patches <gcc-patches@gcc.gnu.org>, richard.sandiford@arm.com
Subject: Re: [PATCH] Put absolute address jump table in data.rel.ro.local if targets support relocations
Date: Mon, 28 Sep 2020 08:52:51 +0800 [thread overview]
Message-ID: <fa9a3756-22d3-45da-51ce-4dea283580e4@linux.ibm.com> (raw)
In-Reply-To: <b66686d7-6796-fcc3-b3b4-2a5f1c3ba197@linux.ibm.com>
Hi,
Gentle ping this:
https://gcc.gnu.org/pipermail/gcc-patches/2020-September/553809.html
Thanks
Gui Haochen
On 14/9/2020 上午 11:01, HAO CHEN GUI wrote:
> Hi,
>
> Jump tables are put into text or rodata section originally. On some
> platforms, it gains the performance benefit from absolute address jump
> tables. So I want to let absolute address jump table be relocatable.
> This patch puts absolute jump table in read only relocation section if
> the target supports relocations.
>
> /* Judge if it's a absolute jump table. Set relocatable for
> absolute jump table if the target supports relocations. */
>
> if (!CASE_VECTOR_PC_RELATIVE
> && !targetm.asm_out.generate_pic_addr_diff_vec ())
> relocatable = targetm.asm_out.reloc_rw_mask ();
>
> switch_to_section (targetm.asm_out.function_rodata_section
>
> (current_function_decl,
> relocatable));
>
> The attachments are the patch diff file and change log file.
>
> Bootstrapped and tested on powerpc64le-linux-gnu with no regressions.
> Is this okay for trunk? Any recommendations? Thanks a lot.
>
next prev parent reply other threads:[~2020-09-28 0:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 3:01 HAO CHEN GUI
2020-09-28 0:52 ` HAO CHEN GUI [this message]
2020-10-01 17:47 ` Richard Sandiford
2020-10-22 2:53 ` HAO CHEN GUI
2020-11-06 1:06 ` HAO CHEN GUI
2020-11-13 9:27 ` Richard Sandiford
2020-11-17 5:57 ` HAO CHEN GUI
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=fa9a3756-22d3-45da-51ce-4dea283580e4@linux.ibm.com \
--to=guihaoc@linux.ibm.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).