kevinlzh1108 wrote: > Did you use AI to write the PR description and/or the code? If so, you need > to disclose it: https://llvm.org/docs/AIToolPolicy.html > > Please add "Fixes #181298 " to the PR message so github will autoclose that > issue if this PR is merged (it isn't enough to just write "Related to > #181298" in a separate comment) > > I've added some other people, since I'm not super qualified to review this > area of the code. With that being said...
> Did you use AI to write the PR description and/or the code? If so, you need > to disclose it: https://llvm.org/docs/AIToolPolicy.html > > Please add "Fixes #181298 " to the PR message so github will autoclose that > issue if this PR is merged (it isn't enough to just write "Related to > #181298" in a separate comment) > > I've added some other people, since I'm not super qualified to review this > area of the code. With that being said... Thanks for the review and for adding more reviewers! AI disclosure: Yes, I used Claude (Anthropic) to assist with writing the test case and PR description. This is noted in the commit trailer (Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>), per the LLVM AI policy. The core fix in DeclBase.cpp was written by me based on my analysis of the bug. I've updated the PR description to include Fixes #181298 so GitHub will auto-close the issue on merge. https://github.com/llvm/llvm-project/pull/181482 _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
