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 10:49:00 -0000	[thread overview]
Message-ID: <9ae1eb49-a759-8c7e-f8fd-01e5d0f245e0@suse.cz> (raw)
In-Reply-To: <a45b078e-0d23-aeec-17bb-e2fdf1dd2c92@arm.com>

[-- Attachment #1: Type: text/plain, Size: 657 bytes --]

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?

Martin

[-- Attachment #2: 0001-Fix-another-failing-test-case.patch --]
[-- Type: text/x-patch, Size: 1505 bytes --]

From e4570be2df2c2fd62d21bca829376670cbb96dc2 Mon Sep 17 00:00:00 2001
From: marxin <mliska@suse.cz>
Date: Tue, 19 Dec 2017 11:47:56 +0100
Subject: [PATCH] Fix another failing test-case.

gcc/testsuite/ChangeLog:

2017-12-19  Martin Liska  <mliska@suse.cz>

	* gcc.dg/tree-prof/switch-case-1.c: Scan IPA profile dump
	file instead of expand in order to not mix it with expanded
	tree decision tree for the switch statement.
---
 gcc/testsuite/gcc.dg/tree-prof/switch-case-1.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/gcc/testsuite/gcc.dg/tree-prof/switch-case-1.c b/gcc/testsuite/gcc.dg/tree-prof/switch-case-1.c
index 6a9af083a9a..a5a430a8ed5 100644
--- a/gcc/testsuite/gcc.dg/tree-prof/switch-case-1.c
+++ b/gcc/testsuite/gcc.dg/tree-prof/switch-case-1.c
@@ -1,4 +1,4 @@
-/* { dg-options "-O2 -fdump-rtl-expand-all" } */
+/* { dg-options "-O2 -fdump-ipa-profile-all" } */
 int g;
 
 __attribute__((noinline)) void foo (int  n)
@@ -36,5 +36,5 @@ int main ()
  return 0;
 }
 /* autofdo cannot do that precise execution numbers */
-/* { dg-final-use-not-autofdo { scan-rtl-dump-times ";; basic block\[^\\n\]*count 4000" 2 "expand"} } */
-/* { dg-final-use-not-autofdo { scan-rtl-dump-times ";; basic block\[^\\n\]*count 2000" 1 "expand"} } */
+/* { dg-final-use-not-autofdo { scan-ipa-dump-times ";;   basic block\[^\\n\]*count 4000" 2 "profile"} } */
+/* { dg-final-use-not-autofdo { scan-ipa-dump-times ";;   basic block\[^\\n\]*count 2000" 1 "profile"} } */
-- 
2.14.3


  parent reply	other threads:[~2017-12-19 10:49 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 [this message]
2017-12-19 13:03   ` Sudakshina Das
2017-12-19 13:20     ` Martin Liška

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=9ae1eb49-a759-8c7e-f8fd-01e5d0f245e0@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).