Box64 BOX64_DYNAREC_BIGBLOCK=0 about box64 HOT 2 OPEN

No, I don't know why.
I don't reproduce on my linux dev. machine. At least not with a already created WINEPREFIX. Maybe it's the prefix creation that fails?

BIGBLOCKS control how big the Dynarec blocks will be. The bigger they are, the more optimized the generated code will be, but that will also memory consuption bigger, bigger part of the code might end up in several Dynablocks.

the BIGBLOCKS=0 select the smallest size, and should not have any negative impact in stability. There must be something wrong in the dynarec cache managment of box64. I'm currently working on fixing an issue on RV64 that also impact the Dynarec Cache Managment, so it might be linked. We'll see once I fix the issue.

from box64.

No, I don't know why. I don't reproduce on my linux dev. machine. At least not with a already created WINEPREFIX. Maybe it's the prefix creation that fails?

BIGBLOCKS control how big the Dynarec blocks will be. The bigger they are, the more optimized the generated code will be, but that will also memory consuption bigger, bigger part of the code might end up in several Dynablocks.

the BIGBLOCKS=0 select the smallest size, and should not have any negative impact in stability. There must be something wrong in the dynarec cache managment of box64. I'm currently working on fixing an issue on RV64 that also impact the Dynarec Cache Managment, so it might be linked. We'll see once I fix the issue.

Thank you man. I updated box64 and BIGBLOCK finally works.THANKS A LOT!!!

from box64.