diff options
| author | Duncan P. N. Exon Smith <dexonsmith@apple.com> | 2016-04-04 04:59:56 +0000 |
|---|---|---|
| committer | Duncan P. N. Exon Smith <dexonsmith@apple.com> | 2016-04-04 04:59:56 +0000 |
| commit | 8e65f8ddfd88fa6b88152ee914b36a67c051f610 (patch) | |
| tree | 46bf2f44ff5aa43ab78dda5e1266327f2490944e /llvm/test/CodeGen/X86 | |
| parent | a017306063c847f08a14f8d3bf627dd19e6d79a2 (diff) | |
| download | bcm5719-llvm-8e65f8ddfd88fa6b88152ee914b36a67c051f610.tar.gz bcm5719-llvm-8e65f8ddfd88fa6b88152ee914b36a67c051f610.zip | |
ValueMapper: Remove old FIXMEs; almost NFC
Remove a few old FIXMEs from the original commit of the Metadata/Value
split in r223802. These are commented out assertions to the effect that
calls between mapValue and mapMetadata never return nullptr.
(The only behaviour change is that Mapper::mapSimpleMetadata memoizes
the nullptr return.)
When I originally rewrote the mapping code, I thought we could be
stricter in the new metadata hierarchy and never return nullptr when
RF_NullMapMissingGlobalValues was off. It's still not entirely clear to
me why these assertions failed (a few months ago, I had a theory that I
forgot to write down, but that's helping no one).
Understood or not, I no longer see how these commented-out assertions
would be useful. I'm relegating them to the annals of source control
before making significant changes to ValueMapper.cpp.
llvm-svn: 265282
Diffstat (limited to 'llvm/test/CodeGen/X86')
0 files changed, 0 insertions, 0 deletions

