From: Jakub Jelinek <jakub@redhat.com>
To: Mihail Ionescu <mihail.ionescu@foss.arm.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH][GCC][arm] Add CLI and multilib support for Armv8.1-M Mainline MVE extensions
Date: Sat, 18 Jan 2020 11:12:00 -0000 [thread overview]
Message-ID: <20200118085415.GT10088@tucnak> (raw)
In-Reply-To: <20200117185846.GQ10088@tucnak>
On Fri, Jan 17, 2020 at 07:58:46PM +0100, Jakub Jelinek wrote:
> One is I wonder if it has been bootstrapped, because at least in a cross
> from x86_64-linux to armv7hl-linux-gnueabi I'm seeing:
> ../../gcc/config/arm/arm.c: In function ‘void cmse_nonsecure_call_inline_register_clear()’:
> ../../gcc/config/arm/arm.c:18469:18: warning: unused variable ‘next’ [-Wunused-variable]
> rtx_insn *next, *last, *pop_insn, *after = insn;
> ^~~~
> warning, which I believe in bootstrap would result in
> -Werror=unused-variable error.
Bootstrap found yet another unused variable:
../../gcc/config/arm/vfp.md:1651:17: warning: unused variable 'regname' [-Wunused-variable]
Fixed thusly, committed as obvious to trunk.
2020-01-18 Jakub Jelinek <jakub@redhat.com>
* config/arm/vfp.md (*clear_vfp_multiple): Remove unused variable.
--- gcc/config/arm/vfp.md
+++ gcc/config/arm/vfp.md
@@ -1648,7 +1648,6 @@ (define_insn "*clear_vfp_multiple"
{
int num_regs = XVECLEN (operands[0], 0);
char pattern[30];
- const char *regname;
rtx reg;
strcpy (pattern, \"vscclrm%?\\t{%|\");
Jakub
next prev parent reply other threads:[~2020-01-18 8:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4751ac8f-c9d4-454f-b036-e31e5e456042@DB5EUR03FT064.eop-EUR03.prod.protection.outlook.com>
2019-12-18 14:16 ` Kyrill Tkachov
2019-12-18 17:03 ` Mihail Ionescu
2019-12-18 17:05 ` Kyrill Tkachov
2020-01-17 9:16 ` Jakub Jelinek
2020-01-17 11:25 ` Mihail Ionescu
2020-01-17 20:13 ` Jakub Jelinek
2020-01-18 11:12 ` Jakub Jelinek [this message]
2019-11-08 17:07 Mihail Ionescu
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=20200118085415.GT10088@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mihail.ionescu@foss.arm.com \
/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).