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
$ owi c sv-benchmarks/c/hardware-verification-bv/btor2c-lazyMod.mul6.c
owi-out/btor2c-lazyMod.mul6.c:30:41: warning: shift count >= width of type [-Wshift-count-overflow]
const SORT_5 mask_SORT_5 = (SORT_5)-1 >> (sizeof(SORT_5) * 8 - 64);
^ ~~~~~~~~~~~~~~~~~~~~~~~~~
owi-out/btor2c-lazyMod.mul6.c:31:39: warning: shift count >= width of type [-Wshift-count-overflow]
const SORT_5 msb_SORT_5 = (SORT_5)1 << (64 - 1);
^ ~~~~~~~~
owi-out/btor2c-lazyMod.mul6.c:49:25: warning: implicit conversion from 'long long' to 'SORT_5' (aka 'unsigned long') changes value from 9223372036854775807 to 4294967295 [-Wconstant-conversion]
const SORT_5 var_64 = 9223372036854775807;
~~~~~~ ^~~~~~~~~~~~~~~~~~~
3 warnings generated.
wasm-ld: error: owi-out/btor2c-lazyMod.mul6.o: undefined symbol: __multi3
wasm-ld: error: owi-out/btor2c-lazyMod.mul6.o: undefined symbol: __multi3
run ['/usr/bin/wasm-ld' '-z' 'stack-size=8388608' '--export=_start' '-o'
'owi-out/a.out.wasm' 'owi-out/btor2c-lazyMod.mul6.o'
'[...]/owi/binc/libc.wasm']: exited with 1
The text was updated successfully, but these errors were encountered:
zapashcanon
changed the title
undefined symbol __floatsitf __multf3 __addtf3 __trunctfdf2
undefined symbol __floatsitf __multf3 __addtf3 __trunctfdf2 __multi3 ...
May 7, 2024
I found this issue. It makes me feel like we should stop calling all the tools (clang, llc, wasm-ld, opt, lld...) and simply rely on clang driving all of them.
I asked @filipeom if there was a particular reason for calling all these tools independently and there's none, it was mostly coming from an old Makefile. I made a tentative PR at #265, I managed to use it on simple files (examples/c/poly.c for instance) with success, but not yet with files using malloc.
(this need #263 to be reproducible, otherwise it fails with other errors IIRC)
The text was updated successfully, but these errors were encountered: