forked from OSchip/llvm-project
1eb4a0da55
This nicely handles the most common case of virtual register sets, but also handles anticipated cases where we will map pointers to IDs. The goal is not to develop a completely generic SparseSet template. Instead we want to handle the expected uses within llvm without any template antics in the client code. I'm adding a bit of template nastiness here, and some assumption about expected usage in order to make the client code very clean. The expected common uses cases I'm designing for: - integer keys that need to be reindexed, and may map to additional data - densely numbered objects where we want pointer keys because no number->object map exists. llvm-svn: 155227 |
||
|---|---|---|
| .. | ||
| ADT | ||
| Analysis | ||
| Bitcode | ||
| ExecutionEngine | ||
| Support | ||
| Transforms | ||
| VMCore | ||
| CMakeLists.txt | ||
| Makefile | ||
| Makefile.unittest | ||