Skip to content

No access to subgroup_min_size, subgroup_max_size #695

@fyellin

Description

@fyellin

This is actually several interlocked bugs that I noticed when playing around with subgroups.

#1) The two classes named GPUAdapterInfo are never actually used. There is no reference to them anywhere else in the code. When creating an Adapter, the current Python code pulls the information it needs out the C structure and then releases the C structure.

#2) The never used class GPUAdapterInfo has properties subgroup_min_size and subgroup_max_size, but there is no such field in the corresponding WGPUAdapterInfo structure. Presumably this is a bug in the Rust -> C interface that this field was forgotten?

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions