about summary refs log tree commit diff
path: root/src/test/codegen/src-hash-algorithm/src-hash-algorithm-md5.rs
diff options
context:
space:
mode:
authorMazdak Farrokhzad <twingoow@gmail.com>2020-03-24 00:49:41 +0100
committerGitHub <noreply@github.com>2020-03-24 00:49:41 +0100
commit72c99f2cf0021fe119dd3de8272349f679188150 (patch)
treec5a6422a7f77abed9bfdb7f3de180c82db9a3a09 /src/test/codegen/src-hash-algorithm/src-hash-algorithm-md5.rs
parenta73ed5aad9afb76bf5ba391641f0cb6c86299242 (diff)
parentb5636b8437feecc3474e607f60891f3ebc098ded (diff)
downloadrust-72c99f2cf0021fe119dd3de8272349f679188150.tar.gz
rust-72c99f2cf0021fe119dd3de8272349f679188150.zip
Rollup merge of #70087 - ecstatic-morse:remove-const-eval-loop-detector, r=RalfJung
Remove const eval loop detector

Now that there is a configurable instruction limit for CTFE (see #67260), we can replace the loop detector with something much simpler. See #66946 for more discussion about this. Although the instruction limit is nightly-only, the only practical way to reach the default limit uses nightly-only features as well (although CTFE will still execute code using such features inside an array initializer on stable).

This will at the very least require a crater run, since it will result in an error wherever the "long running const eval" warning appeared before. We may need to increase the default for `const_eval_limit` to work around this.

Resolves #54384 cc #49980
r? @oli-obk cc @RalfJung
Diffstat (limited to 'src/test/codegen/src-hash-algorithm/src-hash-algorithm-md5.rs')
0 files changed, 0 insertions, 0 deletions