You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This only fails under debug builds, all other build settings work fine. Although, I'm not sure if this just a result of this reproduction as I still get this error when running the zig build --build-file ../build.zig test command when specifying a release setting. Is the zig build build runner always compiled in debug mode?
The p0 must be present for this to fail and further, it appears to need to be a single type larger than 64-bits. If p0 is builtin.TypeId this still fails, but if it is a u64 this code works fine. This is unrelated to the size of the total struct, as 4 individual u32 fields for example will work fine.
The .name field must be set from an argument and not directly via a literal, else this will compile fine.
Assembly
Assembly between Linux and FreeBSD are practically identical so maybe there is some ABI difference that we are missing?
The following code runs and compiles fine under Linux, but fails with a
SIGBUS
on FreeBSD.A few notes:
debug
builds, all other build settings work fine. Although, I'm not sure if this just a result of this reproduction as I still get this error when running thezig build --build-file ../build.zig test
command when specifying a release setting. Is thezig build
build runner always compiled in debug mode?p0
must be present for this to fail and further, it appears to need to be a single type larger than 64-bits. Ifp0
isbuiltin.TypeId
this still fails, but if it is au64
this code works fine. This is unrelated to the size of the total struct, as 4 individualu32
fields for example will work fine..name
field must be set from an argument and not directly via a literal, else this will compile fine.Assembly
Assembly between Linux and FreeBSD are practically identical so maybe there is some ABI difference that we are missing?
FreeBSD option
Will try and dig into this a bit more over the next few days.
The text was updated successfully, but these errors were encountered: