Enrico Granata d4cb1dddeb When I introduced hard-coded formatters, I made them non-cacheable
This is because - in theory - the formatter could match on not just the type, but also other properties of a ValueObject, so a per-type caching would not be a good thing
On the other hand, that is not always true - sometimes the matching truly is per-type

So, introduce a non-cacheable attribute on formatters that decides whether a formatter should or should not be cached. That way, the few formatters that don't want themselves cached can do so, but most formatters (including most hard-coded ones) can cache themselves just fine

llvm-svn: 241184
2015-07-01 20:06:40 +00:00
2015-06-27 12:35:54 +00:00
2015-07-01 12:56:33 +00:00
2015-05-23 15:16:09 +00:00
2015-07-01 15:16:04 +00:00
2015-06-30 08:22:14 +00:00
Description
llvm with tablegen backend for capstone disassembler
2.1 GiB
Languages
LLVM 34.8%
C++ 32.7%
C 19.6%
Assembly 8.6%
MLIR 1.2%
Other 2.7%