Chris Lattner 16af11d962 It turns out that the two dimensional vectors were causing big slowdowns ... in this for programs with lots of types (like the testcase in PR224). The problem was that the type ID that the outer vector was using was not very dense (as many types are getting resolved), so the vector is large and gets reallocated a lot. Since there are a lot of values in the program (the .ll file is 10M), each reallocation has to copy the subvectors, which is also quite slow (this wouldn't be a problem if C++ supported move semantics, but it doesn't, at least not yet :( Changing the outer data structure to a map speeds a release build of llvm-as up from 11.21s to 5.13s on the testcase in PR224. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@11244 91177308-0d34-0410-b5e6-96231b3b80d8		2004-02-09 21:03:38 +00:00
..
.cvsignore
Lexer.l
llvmAsmParser.y	It turns out that the two dimensional vectors were causing big slowdowns	2004-02-09 21:03:38 +00:00
Makefile
Parser.cpp
ParserInternals.h