public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/99888] New: Add powerpc ELFv2 support for -fpatchable-function-entry*
Date: Sat, 03 Apr 2021 08:13:38 +0000 [thread overview]
Message-ID: <bug-99888-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99888
Bug ID: 99888
Summary: Add powerpc ELFv2 support for
-fpatchable-function-entry*
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: jakub at gcc dot gnu.org
CC: amodra at gmail dot com, hjl.tools at gmail dot com,
jakub at gcc dot gnu.org, marxin at gcc dot gnu.org,
seurer at gcc dot gnu.org, unassigned at gcc dot gnu.org
Depends on: 98125
Target Milestone: ---
Host: powerpc64*-linux-gnu
Target: powerpc64*-linux-gnu
Build: powerpc64*-linux-gnu
+++ This bug was initially created as a clone of Bug #98125 +++
As mentioned in PR98125, for ELFv2 the patchable nops need to be added after
the first two insns of the function rather than before it.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98125
[Bug 98125] [11 Regression] New test case g++.dg/pr93195a.C in r11-5656 has
excess errors
next reply other threads:[~2021-04-03 8:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-03 8:13 jakub at gcc dot gnu.org [this message]
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
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@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: 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).