Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 14 Jan 2026 11:14:20 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 292421] emulators/flycast: update to 2.6
Message-ID:  <bug-292421-7788-fCtCdRYybW@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-292421-7788@https.bugs.freebsd.org/bugzilla/>

index | next in thread | previous in thread | raw e-mail

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=292421

--- Comment #2 from Stefan Schlosser <bsdcode@disroot.org> ---
> 1) The port uses the xbyak git submodule with the version pinned in the flycast
> repo instead of the devel/xbyak port, because flycast crashes upon starting a game
> with newer xbyak versions. I still have to investigate this issue and it's not
> clear if it's a regression in xbyak, flycast or somewhere else.
The experienced crash is a thrown exception ERR_BAD_MEM_SIZE from xbyak. This
exception gets thrown after introducing a new check for matching sizes of
register and memory operands in the opMR function:
https://github.com/herumi/xbyak/commit/de4ad6b96434592b9da6a286d717794b5d5f5cf8

This commit was made directly after the pinned submodule version in the flycast
repo, so any newer xbyak version will trigger this exception in flycast.

The macro XBYAK_STRICT_CHECK_MEM_REG_SIZE was introduced later to disable
exactly this check:
https://github.com/herumi/xbyak/commit/86389781d918071b3c35640e082cc76eed400b59

I tested flycast with the devel/xbyak port and setting
XBYAK_STRICT_CHECK_MEM_REG_SIZE=0 for compilation. This prevents the crash.

But this macro has a comment that it may be removed in future version of xbyak,
therefore I currently don't want to depend on it for flycast. Ultimatly,
upstream flycast will have to address this if/when it updates the xbyak
submodule.

In conclusion, we should keep using the xbyak submodule instead of the
devel/xbyak port for now.

-- 
You are receiving this mail because:
You are the assignee for the bug.

home | help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-292421-7788-fCtCdRYybW>