From: Richard Earnshaw <Richard.Earnshaw@foss.arm.com>
To: Christophe Lyon <christophe.lyon@arm.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] arm: Fix warning in libgcc/config/arm/pr-support.c
Date: Fri, 3 Feb 2023 15:34:39 +0000 [thread overview]
Message-ID: <3d9a5c0c-9e20-abe2-0a69-d747ceaa7cc6@foss.arm.com> (raw)
In-Reply-To: <20230201094650.65755-1-christophe.lyon@arm.com>
On 01/02/2023 09:46, Christophe Lyon via Gcc-patches wrote:
> I have noticed some warnings when building GCC for arm-eabi:
> pr-support.c:110:7: warning: variable ‘set_pac_sp’ set but not used [-Wunused-but-set-variable]
> pr-support.c:109:7: warning: variable ‘set_pac’ set but not used [-Wunused-but-set-variable]
>
> This small patch avoids them by defining these two variables undef
> TARGET_HAVE_PACBTI, like the code which actually uses them.
>
> libgcc/
> * config/arm/pr-support.c (__gnu_unwind_execute): Use
> TARGET_HAVE_PACBTI to define set_pac and set_pac_sp.
OK
R.
prev parent reply other threads:[~2023-02-03 15:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 9:46 Christophe Lyon
2023-02-01 9:46 ` [PATCH] arm: [MVE] Add missing length=8 attribute Christophe Lyon
2023-02-03 15:35 ` Richard Earnshaw
2023-02-03 15:34 ` Richard Earnshaw [this message]
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=3d9a5c0c-9e20-abe2-0a69-d747ceaa7cc6@foss.arm.com \
--to=richard.earnshaw@foss.arm.com \
--cc=christophe.lyon@arm.com \
--cc=gcc-patches@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).