likeamahoney wrote: > Hello @likeamahoney ๐ > > Thank you for submitting a Pull Request (PR) to the LLVM Project. Since this > is your first PR, here are a few useful links covering our main contribution > policies and review practices. > > * All contributions to LLVM must follow our [LLVM AI Tool Use > Policy](https://llvm.org/docs/AIToolPolicy.html). In particular, if you used > AI while working on this PR, remember to add a note to the PR description. > * The [LLVM Code-Review Policy and > Practices](https://llvm.org/docs/CodeReview.html) document contains practical > information about the PR process, including how patches are reviewed and > accepted, and who can review a PR. > * Our [LLVM Developer Policy](https://llvm.org/docs/DeveloperPolicy.html) > describes our expectations for code quality, commit summaries and contains > notes on our CI system. > > Please reply to this message to confirm that you have read these policies, > especially the LLVM AI Tool Use Policy, and that any AI tool usage has been > noted in the PR description. > > ### Frequently asked questions > **How do I add reviewers?** > > This PR will be automatically labeled, and the relevant teams will be > notified. For some parts of the project, reviewers may also be added > automatically. > > You can also add reviewers manually using the **Reviewers** section on this > page. If you cannot use that section, it is probably because you do not have > write permissions for the repository. In that case, you can request a review > by tagging reviewers in a comment using `@` followed by their GitHub username. > > **What if there are no comments?** > > If you have not received any comments on your PR after a week, you can > request a review by pinging the PR with a comment such as โPingโ. The common > courtesy ping rate is once a week. Please remember that you are asking for > volunteer time from other developers. > > **Are any special GitHub settings required to contribute to LLVM?** > > We only require contributors to have a public email address associated with > their GitHub commits, see this > [section](https://llvm.org/docs/DeveloperPolicy.html#email-addresses) of LLVM > Developer Policy for details. > > If you have questions, feel free to leave a comment on this PR, or ask on > [LLVM Discord](https://discord.com/invite/xS7Z362) or [LLVM > Discourse](https://discourse.llvm.org/). > > Thank you, The LLVM Community
I have read the [LLVM AI Tool Use Policy](https://llvm.org/docs/AIToolPolicy.html). I used an AI assistant (Claude by Anthropic) in two limited ways during this contribution: **Verification**. After independently diagnosing the root cause and writing the fix, I used the AI to cross-check my reasoning - specifically, that rebuilding the qualifier as `DependentNameType` is the correct recovery and that the fix does not affect out-of-line declarator paths. I reviewed all output myself and am fully confident in the implementation. **Issue discovery**. I encountered the crash independently while working on a SystemVerilog toolchain. The AI helped me locate the existing upstream issue [#174301](https://github.com/llvm/llvm-project/issues/174301), which I had not found on my own before writing the fix. The fix, the test cases, and the PR description were written by me. I can answer questions about the implementation during review. https://github.com/llvm/llvm-project/pull/205762 _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
