From: Thomas Preudhomme <thomas.preudhomme@foss.arm.com>
To: Christophe Lyon <christophe.lyon@linaro.org>,
Jan Hubicka <hubicka@ucw.cz>
Cc: Jeff Law <law@redhat.com>, Richard Biener <rguenther@suse.de>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: Early jump threading
Date: Tue, 20 Sep 2016 08:41:00 -0000 [thread overview]
Message-ID: <6d883990-95ba-60d3-a83b-ea9e84d412fe@foss.arm.com> (raw)
In-Reply-To: <CAKdteOZOq1VSbUYfSHfOTjy=+k_sEskBRmBQEfrz+BSqUXkpPQ@mail.gmail.com>
On 19/09/16 08:02, Christophe Lyon wrote:
>> Index: testsuite/gcc.dg/tree-ssa/pr68198.c
>> ===================================================================
>> --- testsuite/gcc.dg/tree-ssa/pr68198.c (revision 240109)
>> +++ testsuite/gcc.dg/tree-ssa/pr68198.c (working copy)
>> @@ -1,5 +1,5 @@
>> /* { dg-do compile } */
>> -/* { dg-options "-O2 -fdump-tree-thread1-details" } */
>> +/* { dg-options "-O2 -fdump-tree-thread1-details -fdisable-tree-ethread" } */
>>
>> extern void abort (void);
>>
>> @@ -40,4 +40,4 @@ c_finish_omp_clauses (tree clauses)
>> /* There are 3 FSM jump threading opportunities, two of which will
>> get filtered out. */
>> /* { dg-final { scan-tree-dump-times "Registering FSM" 1 "thread1"} } */
>> -/* { dg-final { scan-tree-dump-times "FSM Thread through multiway branch without threading a multiway branch" 2 "thread1"} } */
>> +/* { dg-final { scan-tree-dump-times "FSM Thread through multiway branch without threading a multiway branch" 2 "ethread"} } */
>
> This test does not work, at least on arm* and aarch64*. I'm seeing:
> cc1: note: disable pass tree-ethread for functions in the range of [0,
> 4294967295]
>
> PASS: gcc.dg/tree-ssa/pr68198.c (test for excess errors)
> PASS: gcc.dg/tree-ssa/pr68198.c scan-tree-dump-times thread1 "Registering FSM" 1
> gcc.dg/tree-ssa/pr68198.c: dump file does not exist
> UNRESOLVED: gcc.dg/tree-ssa/pr68198.c scan-tree-dump-times ethread
> "FSM Thread through multiway branch without threading a multiway
> branch" 2
Shouldn't the test enable tree-ethread to have a ethread dump?
Best regards,
Thomas
next prev parent reply other threads:[~2016-09-20 8:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-11 14:02 Jan Hubicka
2016-08-11 14:06 ` Richard Biener
2016-08-11 14:27 ` Jan Hubicka
2016-08-11 15:50 ` Richard Biener
2016-08-11 18:42 ` Jeff Law
2016-09-18 19:30 ` Jan Hubicka
2016-09-19 6:53 ` Andrew Pinski
2016-09-19 9:29 ` Jan Hubicka
2016-10-18 15:56 ` James Greenhalgh
2016-12-15 11:54 ` [Patch] Undermine the jump threading cost model to fix PR77445 James Greenhalgh
2016-12-16 12:34 ` Richard Biener
2016-09-19 7:59 ` Early jump threading Christophe Lyon
2016-09-20 8:41 ` Thomas Preudhomme [this message]
2016-08-11 18:41 ` Jeff Law
2016-08-12 6:02 ` Richard Biener
2016-08-15 17:06 ` Jeff Law
2016-08-11 18:30 ` Jeff Law
2016-08-11 18:29 ` Jeff Law
2016-08-16 11:02 ` Jan Hubicka
2016-08-16 15:42 ` Jeff Law
2016-08-12 8:02 ` Richard Biener
2016-08-12 11:27 ` Jan Hubicka
2016-08-15 17:25 ` Jeff Law
2016-08-16 16:52 ` Jeff Law
2016-08-18 19:55 ` Jeff Law
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=6d883990-95ba-60d3-a83b-ea9e84d412fe@foss.arm.com \
--to=thomas.preudhomme@foss.arm.com \
--cc=christophe.lyon@linaro.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=law@redhat.com \
--cc=rguenther@suse.de \
/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).