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 libgcc/103004] [12 regression] r12-4416 breaks backtrace on PPC64 Big-endian
Date: Tue, 09 Nov 2021 10:54:22 +0000 [thread overview]
Message-ID: <bug-103004-4-N5LtEwmuNn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103004-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103004
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I think the warning should be fixed with following, just need to test it:
--- libgcc/config/rs6000/linux-unwind.h.jj 2021-10-15 11:59:16.227682621
+0200
+++ libgcc/config/rs6000/linux-unwind.h 2021-11-09 11:42:06.840353422 +0100
@@ -395,7 +395,8 @@ struct frame_layout
};
-void ppc_backchain_fallback (struct _Unwind_Context *context, void *a)
+static void
+ppc_backchain_fallback (struct _Unwind_Context *context, void *a)
{
struct frame_layout *current;
struct trace_arg *arg = a;
next prev parent reply other threads:[~2021-11-09 10:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-30 16:39 [Bug libgcc/103004] New: [12 regression] breaks lots on powerpc BE seurer at gcc dot gnu.org
2021-10-31 1:50 ` [Bug libgcc/103004] " pinskia at gcc dot gnu.org
2021-11-02 8:14 ` [Bug libgcc/103004] [12 regression] r12-4416 breaks backtrace on PPC64 Big-endian rguenth at gcc dot gnu.org
2021-11-03 17:34 ` dje at gcc dot gnu.org
2021-11-09 10:40 ` redi at gcc dot gnu.org
2021-11-09 10:54 ` jakub at gcc dot gnu.org [this message]
2021-11-10 22:01 ` rzinsly at linux dot ibm.com
2021-11-11 15:36 ` segher at gcc dot gnu.org
2021-11-11 16:56 ` segher 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-103004-4-N5LtEwmuNn@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).