[libc-commits] [clang] [libc] [llvm] [clang] Make __builtin_exp and __builtin_expf constexpr. (PR #199808)

[Aaron Ballman via libc-commits]

AaronBallman wrote:

> Hi! This comment was generated using [fuzz-fill](https://github.com/ROCm/fuzz-fill), a new tool we're building to help improve LLVM test coverage by spotting lines introduced in a PR that don't yet appear to be exercised by the full test suite, including any tests added in this PR.

@mgcarrasco thank you for the comment! I'm not certain if this is using an LLM or not, but the "this comment was generated" tickled my dangersense so I'd like to verify this tool conforms to our AI policy (https://llvm.org/docs/AIToolPolicy.html), in particular:

> An important implication of this policy is that it bans agents that take action in our digital spaces without human approval, such as the GitHub [@claude agent](https://github.com/claude/). Similarly, automated review tools that publish comments without human review are not allowed.

Is this tool fully automated, or is there a human in the loop verifying everything the tool wants to say before it is posted?

Also, was there an RFC somewhere about the tool or its strategy? Personally, I like the tool so far and I think it's a good idea in general so long as there's a human in the loop with it. This kind of feedback on PRs has the potential to be incredibly useful! I just want to make sure there is community buy-in before the tool goes hog-wild on every PR in the project.

https://github.com/llvm/llvm-project/pull/199808