Skip to content

Fix bugs in llm-relay overwriting ops + repeating file names #127

@PaliC

Description

@PaliC

Overwriting Ops

Currently llm-relay defines it's backend as a dictionary of { op_name: compiled_kernel }. Unfortunately, from the way it grabs the op_name multiple distinct ops can have the same name (an example is aten.div.Tensor_mode which is the name of two seperate ops).

  • Investigate the differences between these ops
  • If separate kernels are warranted, ensure that llm-relay actually writes separate kernels for these, otherwise, have llm-relay generate a single kernel for the set of ops and reflect that in the reporting.

Overwriting Files

A bigger issue is that we are overwriting files when there is a different overload. For example with div we have 2 separate overloads, but only the result for aten.div.Tensor_mode shows up. Fortunately, this is an easy solve.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions