Skip to content

Clarify intended codegen model for dcompute.std.sync.barrier() #95

@gulugulubing

Description

@gulugulubing

Currently dcompute.std.index exposes device helpers as template/property functions, e.g. GlobalIndex.x()(), so the helper body is instantiated into the importing kernel module, without compiling the dcompute's source code.
By contrast, dcompute.std.sync.barrier() is currently a normal function, which means it should be explicitly compiled.

So is it more reasonable to change dcompute.std.sync.barrier() to a zero-argument template like GlobalIndex.x()()?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions