public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug tree-optimization/18507] New: block_defs_stack varrray should not be GC'ed
@ 2004-11-15 23:05 pinskia at gcc dot gnu dot org
  2004-11-16 15:53 ` [Bug tree-optimization/18507] " pinskia at gcc dot gnu dot org
                   ` (4 more replies)
  0 siblings, 5 replies; 6+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2004-11-15 23:05 UTC (permalink / raw)
  To: gcc-bugs

For the testcase in PR 13776 (ir.ii) we spend a lot of time (10% out of 120 seconds) in ggc_alloc.
Most of that time comes from creatting/expanding the block_defs_stack varray in tree-into-ssa.c
Why is this GC allocated in the first place?
Maybe this should be a non-gc'ed VEC.
We know that this varray does not spill out from rewrite_blocks/rewrite_ssa_into_ssa at all.

-- 
           Summary: block_defs_stack varrray should not be GC'ed
           Product: gcc
           Version: 4.0.0
            Status: UNCONFIRMED
          Keywords: compile-time-hog
          Severity: minor
          Priority: P2
         Component: tree-optimization
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: pinskia at gcc dot gnu dot org
                CC: gcc-bugs at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18507


^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2004-12-01  0:50 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-11-15 23:05 [Bug tree-optimization/18507] New: block_defs_stack varrray should not be GC'ed pinskia at gcc dot gnu dot org
2004-11-16 15:53 ` [Bug tree-optimization/18507] " pinskia at gcc dot gnu dot org
2004-11-17 16:00 ` pinskia at gcc dot gnu dot org
2004-11-19 18:22 ` pinskia at gcc dot gnu dot org
2004-11-19 18:22 ` cvs-commit at gcc dot gnu dot org
2004-12-01  0:50 ` pinskia at gcc dot gnu dot org

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).