public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Giuliano Belinassi <giulianob@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc(refs/users/giulianob/heads/pfe_backport)] Backport targhooks.c (default_print_patchable_function_entry): Emit __patchable_function_entries sec Date: Mon, 25 Oct 2021 15:06:24 +0000 (GMT) [thread overview] Message-ID: <20211025150624.6F6E33857007@sourceware.org> (raw) https://gcc.gnu.org/g:2d35914acc611b8780c52c2e6df78d56da37a61d commit 2d35914acc611b8780c52c2e6df78d56da37a61d Author: Joao Moreira <jmoreira@suse.de> Date: Wed Apr 17 18:24:23 2019 +0000 Backport targhooks.c (default_print_patchable_function_entry): Emit __patchable_function_entries section with writable flags to allow... gcc/ChangeLog 2021-10-07 Giuliano Belinassi <gbelinassi@suse.de> Backport from mainline 2019-04-10 Joao Moreira <jmoreira@suse.de> * targhooks.c (default_print_patchable_function_entry): Emit __patchable_function_entries section with writable flags to allow relocation resolution. Diff: --- gcc/targhooks.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/targhooks.c b/gcc/targhooks.c index c57967966c5..be0c557f1a2 100644 --- a/gcc/targhooks.c +++ b/gcc/targhooks.c @@ -1643,7 +1643,7 @@ default_print_patchable_function_entry (FILE *file, ASM_GENERATE_INTERNAL_LABEL (buf, "LPFE", patch_area_number); switch_to_section (get_section ("__patchable_function_entries", - 0, NULL)); + SECTION_WRITE | SECTION_RELRO, NULL)); fputs (asm_op, file); assemble_name_raw (file, buf); fputc ('\n', file);
next reply other threads:[~2021-10-25 15:06 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-25 15:06 Giuliano Belinassi [this message] -- strict thread matches above, loose matches on Subject: below -- 2021-10-11 20:49 Giuliano Belinassi
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=20211025150624.6F6E33857007@sourceware.org \ --to=giulianob@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.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: linkBe 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).