glam v0.33.6 breaks `Vec3A`
@Firestar99 ya está trabajando en esto.
Desde el 22/9/2026.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
PR https://github.com/bitshifter/glam-rs/pull/786 changed the definition of Vec3A to make it bytemuck::Pod:
#[repr(align(16))]
#[repr(C)]
#[cfg_attr(target_arch = "spirv", rust_gpu::vector::v1)]
pub struct Vec3A {
pub x: f32,
pub y: f32,
pub z: f32,
+ _w: f32,
}
So from rust-gpu's perspective, this is now a vector with 4 floats instead of 3 floats, breaking a lot of safety assumptions in our codebase.
Observed Fallout
- breaks rust-gpu's
Matrix4x3layout, causing certain raytracing-related intrinsics to miscompile into invalid spirv. See compiletestray_query_get_intersection_object_to_world_khrbreaking after glam update, as seen in this CI of PR https://github.com/Rust-GPU/rust-gpu/pull/630 - This CI of PR https://github.com/Rust-GPU/rust-gpu/pull/646 shows compiletest
sample_gradientfailing, showing potential higher fallout:
error: error:0:0 - Expected Image Operand Grad dx to have 3 components, but given 4
%38 = OpImageSampleDrefExplicitLod %float %37 %32 %float_1 Grad %33 %34
Mitigation
Problems:
- glam v0.33.6 is a breaking change for rust-gpu
- glam added
_w: f32member to getimpl bytemuck::Pod for Vec3A, so reverting this is a breaking change for regular glam users - don't want
impl Podnot to be impl on spirv
Ideas:
- hack something in the compiler to special case
glam::Vec3A- how do we know if a type is
Vec3A? This will be a hack and not really sustainable
- how do we know if a type is
- PR https://github.com/Rust-GPU/rust-gpu/pull/646 adjusts
Matrix4x3to useVec3instead ofVec3A. The layout of that special type is screwed up anyway, so we don't really care about it changing.- not a full mitigation!
Strategy:
- short term fix
- special case spirv to not have
_w: f32member and not implPod, - release glam v0.33.9, fixing rust-gpu
- long term fix
glam::Vec3A:- remove short term fix
- change attribute to
#[spirv::vector::v1(3, f32)]to overwrite rust-gpu vector type - release glam v0.34.0
- rust-gpu:
- adjust
#[spirv::vector::v1]attribute to take params to overwrite vector type - make rust-gpu support glam v0.34.0
- release rust-gpu?
- adjust
will update this description as I go
- Lenguaje dominante
- Rust
- Estrellas
- 3.4k
- Forks
- 126
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de Rust-GPU/rust-gpu
-
enhancement
Dificultad 1/5 Menos de una hora Aptitud para principiantes 68/100
-
enhancement
Rust-GPU/rust-gpu#643 · 3 comentarios · 1 reacción · 1 asignado ·
-
bug
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
-
bug
Dificultad 3/5 1-2 días Aptitud para principiantes 48/100
-
async functions cause ICE Abiertobug
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
Todos los issues de Rust-GPU/rust-gpu
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
agentic-workflows
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
web-infra-dev/rspack#15847 ·