From: "Andre Vieira (lists)" <Andre.SimoesDiasVieira@arm.com>
To: gcc-patches@gcc.gnu.org
Cc: Ramana Radhakrishnan <Ramana.Radhakrishnan@arm.com>,
Kyrill Tkachov <kyrylo.tkachov@arm.com>
Subject: [Ping 2][PATCH][ARM] Updating testcase unsigned-extend-2.c
Date: Wed, 21 Dec 2016 12:08:00 -0000 [thread overview]
Message-ID: <585A7018.8000404@arm.com> (raw)
In-Reply-To: <584EB228.9050600@arm.com>
On 12/12/16 14:20, Andre Vieira (lists) wrote:
> On 21/06/16 15:16, Andre Vieira (lists) wrote:
>> Hello,
>>
>> After some changes to GCC this test no longer tests the desired code
>> generation behavior. The generated assembly is better than it used to
>> be, but it has become too smart. I add an extra parameter to make sure
>> GCC can't optimize away the loop.
>>
>> Tested for arm-none-eabi-gcc with a Cortex-M3 target.
>>
>> Is this OK?
>>
>> Cheers,
>> Andre
>>
>> gcc/ChangeLog
>> 2016-06-21 Andre Vieira <andre.simoesdiasvieira@arm.com>
>>
>> * gcc.target/arm/unsigned-extend-2.c: Update testcase.
>>
>
> Ping.
>
Ping.
next prev parent reply other threads:[~2016-12-21 12:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 14:16 [PATCH][ARM] " Andre Vieira (lists)
2016-12-12 14:20 ` [Ping][PATCH][ARM] " Andre Vieira (lists)
2016-12-21 12:08 ` Andre Vieira (lists) [this message]
2016-12-21 12:09 ` [PATCH][ARM] " Kyrill Tkachov
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=585A7018.8000404@arm.com \
--to=andre.simoesdiasvieira@arm.com \
--cc=Ramana.Radhakrishnan@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kyrylo.tkachov@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).