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/99889] Add powerpc ELFv1 support for -fpatchable-function-entry* with "o" sections
Date: Sat, 03 Apr 2021 08:16:26 +0000 [thread overview]
Message-ID: <bug-99889-4-3zFRTSVKvh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99889-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99889
Bug 99889 depends on bug 98125, which changed state.
Bug 98125 Summary: [11 Regression] New test case g++.dg/pr93195a.C in r11-5656 has excess errors
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98125
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
next prev parent reply other threads:[~2021-04-03 8:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-03 8:15 [Bug target/99889] New: " jakub at gcc dot gnu.org
2021-04-03 8:16 ` jakub at gcc dot gnu.org [this message]
2022-08-12 7:57 ` [Bug target/99889] " linkw at gcc dot gnu.org
2022-09-30 12:35 ` linkw at gcc dot gnu.org
2022-11-25 3:21 ` cvs-commit at gcc dot gnu.org
2022-11-25 6:18 ` linkw at gcc dot gnu.org
2023-07-21 5:49 ` linkw 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-99889-4-3zFRTSVKvh@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).