aboutsummaryrefslogtreecommitdiff
path: root/llvm/unittests/Support/SourceMgrTest.cpp
diff options
context:
space:
mode:
authorTsche <2440422+Tsche@users.noreply.github.com>2025-10-13 17:53:06 +0200
committerGitHub <noreply@github.com>2025-10-13 11:53:06 -0400
commitec2d6add367acbc03dba038b7d4e519b11bbadec (patch)
tree632297afda6bfba657594868d4e150f7a78d5b32 /llvm/unittests/Support/SourceMgrTest.cpp
parent1820102167a5ace14a5c1f79d11d5eb4cce93001 (diff)
downloadllvm-ec2d6add367acbc03dba038b7d4e519b11bbadec.zip
llvm-ec2d6add367acbc03dba038b7d4e519b11bbadec.tar.gz
llvm-ec2d6add367acbc03dba038b7d4e519b11bbadec.tar.bz2
[clang] introduce constexpr step limit opt-out (#160440)
To address @AaronBallman's feedback from https://github.com/llvm/llvm-project/pull/143785 this patch implements an explicit opt-out for `-fconstexpr-steps` by setting `-fconstexpr-steps=0`. This does not change any defaults, but gives users an easy way to opt out of this limit altogether (and instead let the compiler reach the system's resource limits). Currently users set `constexpr-steps` to some arbitrary high number (and I mean _arbitrary_ - see the tables in the previous PR). This isn't actually opting out of the limit though - you're still bound by the upper bound of the counter's type. If you have enough resources to evaluate more than 18446744073709551615 steps that's bad news. In any case, `=0` conveys the intent clearer. This is in line with how we handle other flags, ie `-ftemplate-backtrace-limit` or `-ferror-limit`.
Diffstat (limited to 'llvm/unittests/Support/SourceMgrTest.cpp')
0 files changed, 0 insertions, 0 deletions