summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Fuzzer/test/FuzzerUnittest.cpp
diff options
context:
space:
mode:
authorPhilip Reames <listmail@philipreames.com>2015-12-19 02:38:22 +0000
committerPhilip Reames <listmail@philipreames.com>2015-12-19 02:38:22 +0000
commit5d54689bcaeeca8845c57418ab63d7cdd0a7e38c (patch)
treee489d1e563a7772cab0d70b5fe3a8d6b31138149 /llvm/lib/Fuzzer/test/FuzzerUnittest.cpp
parent45784a79fc700da169f42b6d88cfb1f3b87c64dc (diff)
downloadbcm5719-llvm-5d54689bcaeeca8845c57418ab63d7cdd0a7e38c.tar.gz
bcm5719-llvm-5d54689bcaeeca8845c57418ab63d7cdd0a7e38c.zip
[RS4GC] Remove an overly strong assertion
As shown by the included test case, it's reasonable to end up with constant references during base pointer calculation. The code actually handled this case just fine, we only had the assert to help isolate problems under the belief that constant references shouldn't be present in IR generated by managed frontends. This turned out to be wrong on two fronts: 1) Manual Jacobs is working on a language with constant references, and b) we found a case where the optimizer does create them in practice. llvm-svn: 256079
Diffstat (limited to 'llvm/lib/Fuzzer/test/FuzzerUnittest.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud