public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Martin Liška" <mliska@suse.cz>
To: Sudakshina Das <sudi.das@arm.com>,
	"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: nd <nd@arm.com>, hubika@ucw.cz
Subject: Re: Replying to an older patch ([PATCH] Fix failing test-case)
Date: Tue, 19 Dec 2017 13:20:00 -0000	[thread overview]
Message-ID: <b12e51df-b50a-9442-b40e-0880bb8c450f@suse.cz> (raw)
In-Reply-To: <b8f007ee-c055-0186-e028-90037f1af81c@arm.com>

On 12/19/2017 02:03 PM, Sudakshina Das wrote:
> Hi Martin
> 
> On 19/12/17 10:49, Martin Liška wrote:
>> On 11/30/2017 12:03 PM, Sudakshina Das wrote:
>>> https://gcc.gnu.org/ml/gcc-patches/2017-10/msg01157.html
>>>
>>> This patch fixed a test case switch-case-2.c. I am seeing switch-case-1.c failing on
>>>
>>> arm-none-linux-gnueabihf:
>>> FAIL: gcc.dg/tree-prof/switch-case-1.c scan-rtl-dump-times expand ";; basic block[^\\n]*count 2000" 1 (found 0 times)
>>>
>>> aarch64-none-linux-gnu:
>>> FAIL: gcc.dg/tree-prof/switch-case-1.c scan-rtl-dump-times expand ";; basic block[^\\n]*count 2000" 1 (found 2 times)
>>>
>>> which looks pretty similar (also the same changes make it pass). Can you confirm?
>>>
>>> Sudi
>>
>> Hello.
>>
>> There's patch for that. Can you please test it?
>>
> 
> I have tested these changes and the test case passes for both arm-none-linux-gnueabihf and aarch64-none-linux-gnu.

Good, thanks for testing. It's quite obvious patch and I'm going to install it.

Martin

> 
> Thanks
> Sudi
> 
>> Martin
>>
> 

      reply	other threads:[~2017-12-19 13:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-30 11:10 Sudakshina Das
2017-11-30 11:38 ` Sudakshina Das
2017-12-19 10:49 ` Martin Liška
2017-12-19 13:03   ` Sudakshina Das
2017-12-19 13:20     ` Martin Liška [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=b12e51df-b50a-9442-b40e-0880bb8c450f@suse.cz \
    --to=mliska@suse.cz \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hubika@ucw.cz \
    --cc=nd@arm.com \
    --cc=sudi.das@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).