This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug rtl-optimization/33922] [4.3 Regression] slow compilation on ia64 (postreload scheduling)
- From: "jakub at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 28 Oct 2007 19:42:03 -0000
- Subject: [Bug rtl-optimization/33922] [4.3 Regression] slow compilation on ia64 (postreload scheduling)
- References: <bug-33922-12387@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #16 from jakub at gcc dot gnu dot org 2007-10-28 19:42 -------
Haven't analyzed why exactly there are so many more safe_group_barrier_needed
calls, but they are certainly much more common than direct group_barrier_needed
calls on this testcase (14579701 safe_group_barrier_needed calls,
14604168 group_barrier_needed calls). But if so, the only thing that call
cares about is the return value, all the state is thrown away. From what I see
the need_barrier retval is ored together from all the recursive calls, couldn't
we gain something by just returning 1 immediately whenever one of the recursive
calls returned non-zero?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33922