Launch any game through pcsrx: pcsxr: ../libpcsxcore/ix86_64/ix86-64.c:160: MEMADDR_OP: Assertion `\!isreg || reg \!= X86_TEMP' failed. This behavior can be observed only when using dynarec (Config.CPU = 0) An easy workaround is to set/force Config.CPU = 1 A better way is disabling PIE 1/ through profile 2/ within the ebuild by disabling PIE through flag-o-matic a "pie" flag could control the required compile flags There's already an upstream bug about this: https://pcsxr.codeplex.com/workitem/12230 P.S.: codeplex bug tracker is not very accessible, unroll "Assertion failure in ix86-64.c with Linux >=4.1.0"
*** Bug 655470 has been marked as a duplicate of this bug. ***
I've just revived the package. I can reproduce the problem with the current release ebuild but the -9999 I've just added seems to work. Could you try it? I'll make a snapshot if it solves the problem for you as well.
Until now adding --no-pie to {C,CXX,LD}FLAGS via /etc/portage/env worked here. After migrating to 17.1 there were at most five package relying on the "no-pie" local env, pcsxr is the last one. Tested today with: 62467b86871aee3d70c7445f3cb79f0858ec566e Weird behavior in the gui before launching a game from command line, surely config file diverged. After this first forced launch, everything went fine. Time for snapshot.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=17393d422c1324d7c7c0364ea0205a3b4c6b322b commit 17393d422c1324d7c7c0364ea0205a3b4c6b322b Author: Michał Górny <mgorny@gentoo.org> AuthorDate: 2020-01-12 12:52:51 +0000 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: 2020-01-12 12:59:55 +0000 games-emulation/pcsxr: Bump to 1.9.94_p20190306 snapshot Closes: https://bugs.gentoo.org/647336 Signed-off-by: Michał Górny <mgorny@gentoo.org> games-emulation/pcsxr/Manifest | 1 + .../pcsxr/pcsxr-1.9.94_p20190306.ebuild | 91 ++++++++++++++++++++++ 2 files changed, 92 insertions(+)
