Skip to content

Koka fails on CI with optimizations enabled #11

@marvinborner

Description

@marvinborner

We want the reference benchmarks to be comparable, so it makes sense to run Koka with optimization enabled. However, all Koka benchmarks fail with exit code 132 (SIGILL) when the optimization level is 2/3 instead of 0.

I believe this is because of some missing SIMD instructions, either because of some Docker configuration or because our self-hosted actions runner doesn't support them. It could also be a problem with Koka itself, where it should have some -march=native flag which I couldn't find.

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