Notes about issue variations_from_march_native in unstable
|Suites:||stretch / buster / unstable / experimental|
when packages invoke gcc or g++ with -march=native or -mcpu=native or
-mtune=native, the resulting binaries will vary depending on the build
system's CPU type. When such binaries are built on newer CPUs, they can
cause segfaults when run on older CPUs due to invalid opcode.
See also https://bugzilla.opensuse.org/show_bug.cgi?id=1100677
Packages in 'unstable' known to be affected by this issue:
(the 1/4 most-popular ones (within this issue) are underlined)
Our notes about issues affecting packages are stored in notes.git and are targeted at packages in Debian in 'unstable/amd64' (unless they say otherwise).
A package name displayed with a bold
font is an indication that this package has a note. Visited
packages are linked in green, those which have not been visited are
linked in blue.
# sign after the name of a package
indicates that a bug is filed against it. Likewise, a
+ sign indicates there is a
patch available, a
P means a
pending bug while
# indicates a
closed bug. In cases of several bugs, the symbol is repeated.