[codegen] Track unanalyzed assembly and include it in docs.#3081
[codegen] Track unanalyzed assembly and include it in docs.#3081
Conversation
This is more approachable than the full llvm-mca analysis. gherrit-pr-id: Ged67b8f5ad7d38d9f2eb40adebea8894a1a6a008
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #3081 +/- ##
=======================================
Coverage 91.87% 91.87%
=======================================
Files 20 20
Lines 6057 6057
=======================================
Hits 5565 5565
Misses 492 492 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request enhances the code generation documentation by including raw assembly code alongside the existing machine code analysis. This change provides a more direct and potentially more approachable view of the generated code. The update involves adding new benchmark files containing assembly code, modifying the rustdoc CSS to accommodate a new display column, and updating the test suite to verify the generation of both assembly and machine code analysis outputs. Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Changelog
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request extends the codegen testing and documentation to include raw assembly output, in addition to the existing llvm-mca analysis. This is achieved by refactoring the test runner to handle different output directives (--asm and --mca) and updating the documentation macro to include a new tab for assembly.
The changes are well-structured. I have a few suggestions to improve maintainability and the developer experience when debugging test failures:
- Use a
.asmextension for the generated assembly files for better clarity. This requires changes in two places and renaming the newly added files. - Improve the panic message in the codegen tests to show the actual generated output when a mismatch is found, which will make debugging easier.
This is more approachable than the full llvm-mca analysis.
Latest Update: v6 — Compare vs v5
📚 Full Patch History
Links show the diff between the row version and the column version.
⬇️ Download this PR
Branch
git fetch origin refs/heads/Ged67b8f5ad7d38d9f2eb40adebea8894a1a6a008 && git checkout -b pr-Ged67b8f5ad7d38d9f2eb40adebea8894a1a6a008 FETCH_HEADCheckout
git fetch origin refs/heads/Ged67b8f5ad7d38d9f2eb40adebea8894a1a6a008 && git checkout FETCH_HEADCherry Pick
git fetch origin refs/heads/Ged67b8f5ad7d38d9f2eb40adebea8894a1a6a008 && git cherry-pick FETCH_HEADPull
Stacked PRs enabled by GHerrit.