Skip to content

Conversation

akaashrp
Copy link

@akaashrp akaashrp commented Oct 8, 2025

This PR replaces int64s with int32s in the argsort and parallel_sampling_from_prob kernels when the target is WebGPU (since WGSL does not currently support i64)

Copy link

Summary of Changes

Hello @akaashrp, 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 refactors several GPU kernels, specifically in sampling and sorting routines, to conditionally utilize int32 data types instead of int64 when compiling for WebGPU targets. This modification is crucial for enhancing performance and ensuring broader compatibility on platforms where int64 operations might be less efficient or not fully supported by WebGPU. The changes are implemented with conditional logic, preserving int64 usage for other backend targets.

Highlights

  • Conditional Integer Type Casting: The pull request introduces conditional logic to cast int64 types to int32 specifically when the compilation target is WebGPU. This affects variables and operations within sampling and sorting kernels.
  • WebGPU Performance and Compatibility: By switching to int32 for WebGPU, the changes aim to improve performance and ensure broader compatibility, as int64 support can be less optimized or problematic on some WebGPU implementations.
  • Target-Specific Code Generation: The modifications ensure that int64 types are preserved for other non-WebGPU targets, maintaining existing behavior and performance where int64 is preferred or necessary.
Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates WebGPU kernels to use int32 instead of int64, which is a necessary change for WebGPU compatibility. The changes look correct in principle.

My main feedback is about code duplication and repeated logic. In python/tvm/topi/gpu/sort.py, the logic to determine the integer type based on the target is repeated in several places, leading to code duplication. I've suggested refactoring these parts to define the data type once and reuse it. This pattern is already used in one part of the file, so applying it consistently would improve the code. A broader improvement would be to determine the target and dtype once at the top of the _sort_common function.

Similarly, in python/tvm/relax/backend/gpu_generic/sampling.py, the same expression to determine the integer type is repeated. I've left a comment suggesting to abstract this into a variable for better readability and maintainability.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant