Hi all, I'm porting JSPI to loong64 port, and find an issue that in JSToWasmWrapperHelper <https://source.chromium.org/chromium/chromium/src/+/refs/tags/119.0.6045.214:v8/src/builtins/js-to-wasm.tq;l=559>, a 32-bit value is converted to unsigned then converted to intptr, which leading to a zero-extended value, but on LoongArch64, we need the 32-bit value to be sign-extended in 64-bit registers.
I don't want to change the behavior on other arches, but the builtin is written in torque, I suppose I can't use `V8_TARGET_ARCH_XXX` macro in it, so is there a way to distinguish v8 target arch in torque builtins? Thanks! Yours, Zhao Jiazhong -- -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev --- You received this message because you are subscribed to the Google Groups "v8-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/v8-dev/c2790cc7-513d-4296-8531-f620fe93e038n%40googlegroups.com.
