Rust-GPU / Rust-GPU/rust-gpu

64 bit and 128 bit integers are not supported at all

Ouverte
#359 9 commentaires 2 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

bug
Langage dominant
Rust
Étoiles
3.4k
Forks
126
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

Expected Behaviour

I want to port some code using fixed::FixedI128 to the gpu, so I tried using rust-gpu to avoid needing to re-implement the wheel.

Well, this failed epically.

Figuring out how to use rust-gpu from the docs and examples is impossible, so I looked at rust-gpu-chimera, and I was able to figure out how to use it.

Of course, even though fixed is no-std and does not allocate, it does not compile, so I started to try to clone it locally and monkeypatch any issues until it would build.

But after the errors just never ended, I thought it more prudent to LITERALLY manually dig through the thousands of lines of macro-generated code for fixed and inline all the code I was using.

Of course, this failed because rust-gpu does not ACTUALLY support 128 bit integers.

Of course, the errors don't explicitly say this, instead they say "unsupported type for constant i128" or something else, and never explicitly admit to not supporting 128 bit integers.

Ok, that's really disappointing, but sure I'll rewrite all these functions to work on 64 bit limbs explicitly instead.

Well, actually, rust-gpu does not support 64 bit integers either, so that was a waste of time.

Now the error does sort of explicitly say this: "error: u64 type used without OpCapability Int64".

This is pretty surprising because on 32 bit CPU targets we can use 128 bit ints with reckless abandon and the compiler will just figure it out, but some part of this when translating from rust to llvm ir to spriv is not putting the square peg into the square hole.

Example & Steps To Reproduce

This kernel stub should have the same error, even with none of the implementation actually present:

#[cfg(target_arch = "spirv")]
#[spirv(compute(threads(1024)))]
pub fn bqa_kernel(
    #[spirv(global_invocation_id)] gid: UVec3,
    #[spirv(storage_buffer, descriptor_set = 0, binding = 0)] data: &mut [((u64, i64), i64, i64)],
    #[spirv(push_constant)] param: &BqaParams,
) {
    let thread_id = ThreadId::new(gid.x);
    bqa_helper(thread_id, data, (param.r0, param.r1), param.b_min, param.b_max);
}

we don't even need to look into bqa_helper or any other implementation details, the error will be something like

     Compiling kernel v0.1.0 (/home/hac/projects/rust-gpu-chimera/kernel)
  error: `u64` type used without `OpCapability Int64`
      |
      = note: used by `core::option::Option<i64>`
      = note: used by `((u64, i64), i64, i64)`
      = note: used by unnamed type
      = note: used by unnamed type
  note: used from within GLCompute entry-point `bqa_kernel`
     --> kernel/src/lib.rs:171:5
      |
  171 |     #[spirv(storage_buffer, descriptor_set = 0, binding = 0)] data: &mut [((u64, i64), i64, i64)],
      |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  error: `i64` type used without `OpCapability Int64`

System Info

Rustc version is pinned to nightly-2025-06-23 by rust-gpu-chimera
SPIRV-Tools v2025.3 v2025.3.rc1-0-g33e025681
OS: linux 6.15.8-zen (arch linux)
GPU: Intel Arc B580
I'm using the webgpu backend following rust-gpu-chimera

Guide de contribution

Ouvrir le guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Piste de recherche

Commencez par le point d’entrée kernel/src/lib.rs et reproduisez les diagnostics signalés pour les types de tampon de stockage u64 et i64. Suivez la manière dont les types entiers sont traduits en capacités SPIR-V, et considérez le problème comme résolu lorsque les largeurs d’entiers prises en charge se compilent correctement ou que leurs limitations sont signalées explicitement.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
rust
Domaine
compilers, computer-graphics
Type d'issue
Bug
Difficulté
4/5
Temps estimé
3-5 jours
Activité
À l'abandon
Clarté
Plutôt claire
Accessibilité débutants
35/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.