Skip to content

[hipDNN] Add CLI args to samples for configurable execution #3540

@SamuelReeder

Description

@SamuelReeder

Allow specifying runtime configuration when running samples via command-line arguments. Ideally, they will support the following arguments:

Argument Description Example
--engine-id Preferred engine ID for execution --engine-id 2
--dtype Data type (fp32, fp16, bf16) --dtype fp16
--layout Tensor layout --layout nhwc
--dims Input tensor dimensions --dims 32,64,224,224
Operation-specific Conv: filter, stride, padding, dilation. BN: eps, momentum --filter 3,3 --stride 2,2

Currently, all params are hardcoded and the run() helper iterates through fixed type/layout combinations rather than allowing user selection.

The benefit of these params being specifiable is that plugin devs can easily test their plugin by setting an engine ID and running supported operations.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions