[llvm-commits] Fwd: Patch for review: Speeding up ScheduleDAG computations

[David Greene]

On Wednesday 05 March 2008 21:52, Chris Lattner wrote:

> >> Right, it's very malloc intensive. That's the main issue.
> >
> > So why not define an allocator for it?
>
> See the previous response.

Couldn't an allocator also handle fragmentation and layout?

I agree that the standard containers aren't always optimal but I think it's
a mistake to dismiss them out of hand.  Most of the time we just don't
care because they're not in performance-critical parts of the code 
(understanding that this case IS a performance-critical piece of code).

                                                    -Dave