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 then becomes a call to get_int_type(g, false, 65536) which is above the range of allowed integer bits, and causes an assertion error.
Edit:
Idea for a solution: instead of getting the LLVM type of a specifically sized integer type with N bits, instead we could create the LLVM type [data.pointer.host_int_bytes x i8]. This seems to communicate intent as "byte buffer with specific size" better than a strangely sized integer, while likely needing extremely few changes to support.
The text was updated successfully, but these errors were encountered:
Vexu
added
bug
Observed behavior contradicts documented or intended behavior
stage1
The process of building from source via WebAssembly and the C backend.
labels
Jan 26, 2021
Currently, this compiles fine:
But this crashes the compiler inside the function
get_int_type
:This is because the
host_int_bytes
of ptr's type is8192
, which in the functionresolve_llvm_types_pointer()
is used like this:This then becomes a call to
get_int_type(g, false, 65536)
which is above the range of allowed integer bits, and causes an assertion error.Edit:
Idea for a solution: instead of getting the LLVM type of a specifically sized integer type with N bits, instead we could create the LLVM type
[data.pointer.host_int_bytes x i8]
. This seems to communicate intent as "byte buffer with specific size" better than a strangely sized integer, while likely needing extremely few changes to support.The text was updated successfully, but these errors were encountered: