Skip to content

ScanByte issue with packageimages #4

Description

@jakobnissen

Dear mantainers,

I just found a bug in ScanByte with how it interacts with package images: If the user sets export JULIA_CPU_TARGET=generic, then ScanByte will still emit code for e.g. AVX2, but then the package image will be broken as Julia cannot use the generated instructions.
I fixed this in ScanByte v 0.4.0, but I recommend just doing what I do and check if ENV["JULIA_CPU_TARGET"] is set to something other than "native", and avoid platform-specific code if so.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions