public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Florian Weimer <fw@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r14-4618] or1k: Fix -Wincompatible-pointer-types warning during libgcc build Date: Fri, 13 Oct 2023 07:37:41 +0000 (GMT) [thread overview] Message-ID: <20231013073741.BE4693857713@sourceware.org> (raw) https://gcc.gnu.org/g:cf611de73d829742f67461e2287fa4ec2bf99801 commit r14-4618-gcf611de73d829742f67461e2287fa4ec2bf99801 Author: Florian Weimer <fweimer@redhat.com> Date: Fri Oct 13 09:34:37 2023 +0200 or1k: Fix -Wincompatible-pointer-types warning during libgcc build libgcc/ * config/or1k/linux-unwind.h (or1k_fallback_frame_state): Add missing cast. Diff: --- libgcc/config/or1k/linux-unwind.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libgcc/config/or1k/linux-unwind.h b/libgcc/config/or1k/linux-unwind.h index aa873791daa..37b0c5aef37 100644 --- a/libgcc/config/or1k/linux-unwind.h +++ b/libgcc/config/or1k/linux-unwind.h @@ -51,7 +51,7 @@ or1k_fallback_frame_state (struct _Unwind_Context *context, return _URC_END_OF_STACK; rt = context->cfa; - sc = &rt->uc.uc_mcontext; + sc = (struct sigcontext *) &rt->uc.uc_mcontext; new_cfa = sc->regs.gpr[1]; fs->regs.cfa_how = CFA_REG_OFFSET;
reply other threads:[~2023-10-13 7:37 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20231013073741.BE4693857713@sourceware.org \ --to=fw@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).