Ian Klask
Ian Klask
> since the relocation for the latter is redirected into the relocation for the name of ".aot_stack_sizes" (the section name), I doubt we should redirect "_aot_stack_sizes" also. Sorry I'm a...
Ah I see now. Yes applying that patch for wamrc fixed the "aot_stack_sizes" issue, but now it moves onto the the other symbol which was added by --bounds-checks=1 and fails...
Thank you. **EDIT:** **I realize now no need to compile wamrc for 32 bit in my case. the fixes in aot_loader are intended for the 32bit runtime. With the fixes...
yes I tried with many different arguments. My usual for testing was 10, 25, 30, and 40. This did work at one point since I had a benchmark setup. Hadn't...
I reduced the threashold multiple times and it never logs. I even went down to 1 and nothing. Here is an example of fib(5) with a threshold of 1 on...
Yes, I do use -DWAMR_BUILD_TARGET=X86_32 for my 32bit builds of iwasm
okay that patch does seem to work for 32bit AOT
I'm not sure what has changed but I haven't been able to get win32 AOT working on any 2.0.0+ update. in iwasm when invoke_native is called it seems to jump...
> Sadly for now we don't have much support for Windows lldb, therefore you can't use the debug feature in Windows WAMR IDE. You may try other features to help...
I got debugging working on the windows platform. You do have to build LLDB yourself with the supplied patch, but there's a few other issues I had to clear up...