This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug optimization/13875] [tree-ssa] missed jump thread optimization on the tree-level
- From: "law at redhat dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 8 Apr 2004 23:45:51 -0000
- Subject: [Bug optimization/13875] [tree-ssa] missed jump thread optimization on the tree-level
- References: <20040127051055.13875.dann@godzilla.ics.uci.edu>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From law at redhat dot com 2004-04-08 23:45 -------
Subject: Re: [tree-ssa] missed jump thread
optimization on the tree-level
In message <20040408233646.30099.qmail@sources.redhat.com>, "dann at godzilla d
ot ics dot uci dot edu" writes:
>
>------- Additional Comments From dann at godzilla dot ics dot uci dot edu 20
>04-04-08 23:36 -------
>> What's strange about them? The first is testing if T.3219 != 0 and the sec
>ond
>> is testing of T.3219 != 2. They're rendered kind-of funny in the pretty
>> printer, but they appear to be correct to me.
>
>I was not sure if those tests are just rendered funny by the pretty printer o
>r
>if it's something that implies that 2 comparisons are going to be performed
>for each "if". Other similar tests are not rendered that way, so maybe that
>is what was confusing for me.
We should get one test for each. Though that's probably something that
ought to be verified, probably by looking at the RTL dump. If you send
me the .rtl dump I'd be more than happy to take a looksie and verify
that the RTL expands DTRT.
[ If the RTL expanders don't DTRT, it ought to be trivial to have a pass which
cleans up these kinds of comparisons after TER is complete. ]
jeff
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13875