From: Kyrill Tkachov <kyrylo.tkachov@foss.arm.com>
To: Michael Collison <Michael.Collison@arm.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Cc: nd <nd@arm.com>
Subject: Re: [PATCH][ARM] Fix static analysis warnings in arm backend
Date: Mon, 26 Jun 2017 10:47:00 -0000 [thread overview]
Message-ID: <5950E63E.9050109@foss.arm.com> (raw)
In-Reply-To: <HE1PR0802MB23778330BC51E68FA7A72D7D95D80@HE1PR0802MB2377.eurprd08.prod.outlook.com>
Hi Michael,
On 23/06/17 21:44, Michael Collison wrote:
> This patch cleans up warning messages due to unused variables and overly complicated loop structures.
>
> Okay for trunk?
Ok.
Thanks,
Kyrill
> 2017-03-30 Michael Collison <michael.collison@arm.com>
>
> PR target/68535
> * config/arm/arm.c (gen_ldm_seq): Remove last unnecessary
> set of base_reg
> (arm_gen_movmemqi): Removed unused variable 'i'.
> Convert 'for' loop into 'while' loop.
> (arm_expand_prologue): Remove last unnecessary set of insn.
> (thumb_pop): Remove unused variable 'pushed_words'.
> (thumb_exit): Remove last unnecessary set of regs_to_pop.
prev parent reply other threads:[~2017-06-26 10:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-23 20:44 Michael Collison
2017-06-23 21:37 ` Eric Gallager
2017-06-23 21:43 ` Michael Collison
2017-06-26 10:47 ` Kyrill Tkachov [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=5950E63E.9050109@foss.arm.com \
--to=kyrylo.tkachov@foss.arm.com \
--cc=Michael.Collison@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nd@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).