public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "i at maskray dot me" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/99888] Add powerpc ELFv2 support for -fpatchable-function-entry* Date: Thu, 11 Aug 2022 06:59:55 +0000 [thread overview] Message-ID: <bug-99888-4-cOHjqttes1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99888-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99888 Fangrui Song <i at maskray dot me> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |i at maskray dot me --- Comment #5 from Fangrui Song <i at maskray dot me> --- * There is a restriction on the number of instructions between the function label and the .localentry directive. * For -fpatchable-function-entry=N[,M], M nops must precede the function label. On aarch64/x86/etc, these nops are consecutive. Personally I think this condition can be lifted for PowerPC ELFv2. The runtime library will need to check st_other or do some instruction inspection, which may be fine. nop nop nop foo: .LCF0: .cfi_startproc addis 2,12,.TOC.-.LCF0@ha addi 2,2,.TOC.-.LCF0@l .localentry foo,.-foo nop nop
next prev parent reply other threads:[~2022-08-11 6:59 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-03 8:13 [Bug target/99888] New: " jakub at gcc dot gnu.org 2021-04-03 8:16 ` [Bug target/99888] " jakub at gcc dot gnu.org 2022-08-03 2:53 ` linkw at gcc dot gnu.org 2022-08-03 9:50 ` linkw at gcc dot gnu.org 2022-08-03 18:40 ` segher at gcc dot gnu.org 2022-08-04 8:20 ` linkw at gcc dot gnu.org 2022-08-11 6:59 ` i at maskray dot me [this message] 2022-08-11 9:00 ` linkw at gcc dot gnu.org 2022-08-11 15:27 ` segher at gcc dot gnu.org 2022-08-12 3:00 ` amodra at gmail dot com 2022-08-12 13:02 ` segher at gcc dot gnu.org 2022-08-24 7:13 ` linkw at gcc dot gnu.org 2022-08-24 7:18 ` linkw at gcc dot gnu.org 2022-09-30 12:18 ` cvs-commit at gcc dot gnu.org 2022-09-30 12:34 ` linkw at gcc dot gnu.org 2022-09-30 12:35 ` linkw at gcc dot gnu.org 2024-01-17 13:58 ` matz at gcc dot gnu.org 2024-01-18 5:41 ` linkw at gcc dot gnu.org 2024-01-20 17:17 ` pinskia at gcc dot gnu.org
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=bug-99888-4-cOHjqttes1@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).