Alex

It's the period between Christmas and New Year so its time for #39c3. This was a nice guide to how #fex_emu works. Their "hack" for dealing with memory ordering vs some game engines does raise an eyebrow or two. I would have liked to know more: https://www.youtube.com/watch?v=3yDXyW1WERg

#x86 #arm #emulation #youtube

39C3 - Breaking architecture barriers: Running x86 games and apps on ARM

YouTube
Dec 31 at 5:20pmWeb
Show threadpenguin42Dec 31
@stsquad Oh, yeh that's a hack; debugging memory ordering failures where they haven't done it properly will be a PITA as well - although perhaps they have a mode where they add barriers everywhere?
Show threadAlexDec 31
@penguin42 that seems to be the implication that by default they use barriers unless they detect the game engine. I assume it insists users of the engines use its own atomic primitives?
Show threadpenguin42Dec 31
@stsquad Maybe the game engines are structured enough that they control all the threading and call back to game code to handle events?