Skip to content

Tracking issue: Seeded Randomess #41

@patrick-rivos

Description

@patrick-rivos

The current code base uses a few unseeded random.Random() calls. This causes the generated asm to be non-reproducable. Ideally we would have the user provide a seed to generate random values

Beyond the benefit of reproducible tests, this change also allows developers to see at a glance if a function uses a random value (since it will have rand: random.Random in it's function signature).

Directories with random.* calls

There might be other directories I missed, but I'll revise this issue when I discover them.

Race conditions:

  • Global variable in riscv-common/isa.py
    • This causes a race condition that manifests in label name when generating in multi-processing mode. Doesn't really matter from a correctness standpoint, but prevents comparing hashes of generated tests.

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