Skip to content

Qualify intermediate default globals with the defining module #745

Description

@khatchad

Residual of the parent's repair: the intermediate default globals are now qualified by the declaring class (LayerNormalization_call_default_0), which separates same-named methods of different classes, but the name still omits the defining module. Two modules that each define a class and method with the same names share one global, unioning their defaults across modules. Module-level functions have the same pre-existing weakness (input_fn_default_0). The full fix qualifies with the entity chain the translator already uses for the _defaults_<i> targets (composeEntityName), which carries the script.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingworkstream:algorithmCore analysis algorithm correctness

    Type

    Fields

    No fields configured for Bug.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions