tree 632297afda6bfba657594868d4e150f7a78d5b32
parent 1820102167a5ace14a5c1f79d11d5eb4cce93001
author Tsche <2440422+Tsche@users.noreply.github.com> 1760370786 +0200
committer GitHub <noreply@github.com> 1760370786 -0400
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsFcBAABCAAQBQJo7SBiCRC1aQ7uu5UhlAAAEy0QAB/q1AASKz4Vgd+o7hOZ82hG
 3c8wQo43mAsREaUf23GprxfblW1z9WHDSoQq8Y3wgVOI4n7dIMVaUhalVx7Y4yBs
 oc5U1W0Z8M4vS4m9MK0HIIoTJEfMZKIJUEtkQ0mzqDZ7Dy7MQ1pmIGQmcOe5xF1g
 ITmheK75xN8CXl9T4pFsYSCL+8iD7L9rTD0qZ0JUf54I+HDhHRy1yxwWVuD9bX3O
 VFjbbSmXqRONaUuXjfQeKhGCmkNjBa3wUjajASau0wFBL+OIO/AdN129cSepghv1
 SD1VZwwfEhenYNjzyo06jOLxgBUvz3dq/QAtJcP5zkbdRL4qZamQAYlRw5a5ubO+
 zY/5K9Td10Eb70ZWntXBmYukpm5A9pMyavonGynR1wRjKzJDHPPGrROUqmdC3Or3
 2akWK6Il8ngkJgozSOY4xFNs7XGJ+LAP/QDuttGBDNM/mnKVKzoQOLJh44LiNViz
 8rRkOyMt5Y01gTi4E9oBXkm0qnNC/lVVFQR/AD4jousy2u+UNAv6gIyrDcNm1yHN
 odsFIxowryONyBNyMavXXcApD4tpbDSwzZKjbrYjNmVKgDTSOh/sR5WIcGVA14+x
 eVQz1T0bWHhqJg/VXmaIIdBHh8IqHeBh9oVV9s02yzBkS9Y03u32bJ9OU9gNgKZh
 euVmkmxC/BzhutVSVN1A
 =r+Ho
 -----END PGP SIGNATURE-----
 

[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`.