https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19794
Bug 19794 depends on bug 68548, which changed state.
Bug 68548 Summary: bogus "may be used uninitialized" (predicate analysis)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68548
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19794
Bug 19794 depends on bug 54345, which changed state.
Bug 54345 Summary: jump threading leaks e->aux heap memory
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54345
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19794
Bug 19794 depends on bug 84078, which changed state.
Bug 84078 Summary: false positive for -Wmaybe-uninitialized with __asm__
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84078
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19794
Bug 19794 depends on bug 61428, which changed state.
Bug 61428 Summary: wrong "maybe-uninitialized" (jump threading? predicate
analysis?)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61428
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19794
Bug 19794 depends on bug 78496, which changed state.
Bug 78496 Summary: [7 Regression] Missed opportunities for jump threading
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78496
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19794
Eric Gallager changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #16 from Eric
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19794
Eric Gallager changed:
What|Removed |Added
CC||egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19794
Bug 19794 depends on bug 81165, which changed state.
Bug 81165 Summary: [8 Regression] Regression in GCC-8.0.0's optimizer
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81165
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19794
Bug 19794 depends on bug 70879, which changed state.
Bug 70879 Summary: Missed jump threading opportunity with multiple != conditions
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70879
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19794
Bug 19794 depends on bug 77445, which changed state.
Bug 77445 Summary: [7 Regression] Performance drop after r239219 on coremark
test
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77445
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19794
Bug 19794 depends on bug 18046, which changed state.
Bug 18046 Summary: Missed jump threading optimization
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=18046
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19794
Bug 19794 depends on bug 54742, which changed state.
Bug 54742 Summary: Switch elimination in FSM loop
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54742
What|Removed |Added
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19794
Bug 19794 depends on bug 54742, which changed state.
Bug 54742 Summary: Switch elimination in FSM loop
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54742
What|Removed |Added
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19794
Bug 19794 depends on bug 54742, which changed state.
Bug 54742 Summary: Switch elimination in FSM loop
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54742
What|Removed |Added
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19794
Bug 19794 depends on bug 58698, which changed state.
Bug 58698 Summary: [4.7/4.8/4.9 Regression] Spurious may be used unitialized
warning when compiling with -Os
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58698
What|Removed
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19794
Bug 19794 depends on bug 58455, which changed state.
Bug 58455 Summary: spurious may be used uninitialized warning with -Og
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58455
What|Removed |Added
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19794
Bug 19794 depends on bug 23622, which changed state.
Bug 23622 Summary: Dom jump threading at -O1 confuses branch prediction
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23622
What|Removed |Added
--
Bug 19794 depends on bug 19940, which changed state.
Bug 19940 Summary: Missed jump threading opportunity due to |.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19940
What|Old Value |New Value
--
Bug 19794 depends on bug 18076, which changed state.
Bug 18076 Summary: Missed jump threading optimization
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18076
What|Old Value |New Value
--
Bug 19794 depends on bug 15221, which changed state.
Bug 15221 Summary: a jump threading opportunity blocked by a few intervening
instructions
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15221
What|Old Value |New Value
--
Bug 19794 depends on bug 15352, which changed state.
Bug 15352 Summary: [tree-ssa] missed jump threading opportunity due to lack of
short circuit
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15352
What|Old Value |New Value
--
Bug 19794 depends on bug 19516, which changed state.
Bug 19516 Summary: missed optimization (bool)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19516
What|Old Value |New Value
--
Bug 19794 depends on bug 19804, which changed state.
Bug 19804 Summary: Missed jump threading opportunity on else arm of COND_EXPR
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19804
What|Old Value |New Value
--- Additional Comments From law at redhat dot com 2005-04-22 18:30 ---
The reload bug has been resolved or at least it's in a state where we can
move forward with the jump threading changes.
I've finally got the dynamic branching data which shows pretty much what I
expected -- we
--
Bug 19794 depends on bug 16538, which changed state.
Bug 16538 Summary: Missed jump threading opportunity with struct fields (but
RTL thread_jumps does catch it)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16538
What|Old Value |New Value
--- Additional Comments From steven at gcc dot gnu dot org 2005-04-23
16:58 ---
18832 has no jump threading issues left, says Jeff.
--
What|Removed |Added
--- Additional Comments From law at redhat dot com 2005-04-19 17:59 ---
An update. The jump threading changes are blocked pending resolution of
a semi-latent bug in reload which is exposed by the combination of the
jump threading changes plus the recent merges from TCB.
I'm testing a
--- Additional Comments From law at redhat dot com 2005-04-08 18:19 ---
OK. I'm pretty sure the perl improvements are really just an artifact of
changes in what objects get spilled onto the stack on the offsets of each
particular object.
I can with a small amount of work twiddle
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-04-06
06:38 ---
(In reply to comment #7)
They don't even bear-out on other x86 platforms -- my older P3 and AMD
boxes don't show the same kind of big improvement (they show a small
improvements). However, both of my
--- Additional Comments From law at redhat dot com 2005-04-06 17:41 ---
Subject: Re: [meta-bug] Jump threading
related bugs
On Wed, 2005-04-06 at 06:38 +, pinskia at gcc dot gnu dot org wrote:
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-04-06
--- Additional Comments From law at redhat dot com 2005-04-06 19:21 ---
More info.
It appears that threading one specific jump is responsible for triggering
the big speedup. And it could cause the kind of effects we're seeing.
Basically we're threading a conditional branch to a loop
--- Additional Comments From law at redhat dot com 2005-04-06 00:25 ---
Just more notes on the huge perl speedup with the threading changes...
For reasons yet unknown, we're seeing a lot less L2 cache traffic when perl
is compiled with the threading changes. The decreased L2 traffic
--- Additional Comments From dberlin at gcc dot gnu dot org 2005-04-06
02:05 ---
Subject: Re: [meta-bug] Jump threading
related bugs
On Wed, 2005-04-06 at 00:25 +, law at redhat dot com wrote:
--- Additional Comments From law at redhat dot com 2005-04-06 00:25
--- Additional Comments From law at redhat dot com 2005-04-06 03:21 ---
Subject: Re: [meta-bug] Jump threading
related bugs
On Wed, 2005-04-06 at 02:05 +, dberlin at dberlin dot org wrote:
--- Additional Comments From dberlin at gcc dot gnu dot org 2005-04-06
02:05
--- Additional Comments From law at redhat dot com 2005-04-02 01:31 ---
Some notes on recent poking and prodding.
The big perl speedup is consistent on my P4 -- but perl shows no significant
change on my AMD box. Perl spends ~50% of its time in one routine (regexec)
and, surprise,
--- Additional Comments From law at redhat dot com 2005-03-22 17:12 ---
The EON issue mentioned in my notes from last week is an instability in how IV
opts selects which induction variables to use. Zdenek has a patch which helps
increase the stability of the IV selection code and
--- Additional Comments From law at redhat dot com 2005-03-16 19:24 ---
An update on the new jump threading selection code.
All the base infrastructure is in place (namely the code to avoid creating
irreducible regions). Benchmarking the new selection code has turned up one
issue with
--
Bug 19794 depends on bug 19938, which changed state.
Bug 19938 Summary: Missed jump threading opportunity due to signedness
difference
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19938
What|Old Value |New Value
--
What|Removed |Added
BugsThisDependsOn||19938
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19794
--
What|Removed |Added
BugsThisDependsOn||19940
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19794
--
What|Removed |Added
BugsThisDependsOn||15352
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19794
--
What|Removed |Added
BugsThisDependsOn||16538
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19794
--
What|Removed |Added
BugsThisDependsOn||17116
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19794
--
What|Removed |Added
BugsThisDependsOn||18046
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19794
--
What|Removed |Added
BugsThisDependsOn||18076
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19794
--
What|Removed |Added
BugsThisDependsOn||18832
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19794
--
What|Removed |Added
BugsThisDependsOn||19516
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19794
--
What|Removed |Added
CC||pinskia at gcc dot gnu dot
||org
Status|UNCONFIRMED
--
What|Removed |Added
BugsThisDependsOn||19804
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19794
49 matches
Mail list logo
