JosJuice b3f71f7cdc JitArm64: Allow DoJit at address 0 (fix launching Wii titles) ... JitArm64::DoJit contains a check where it prints a warning and tries to pause emulation if instructed to compile code at address 0. I'm assuming this was done in order to provide a nicer error behavior in cases where PC was accidentally set to null. Unfortunately, it has started causing us problems recently, as 688bd61 writes and runs some code at address 0 to simulate the PPC being held in reset. What makes this worse is that calling Core::SetState from the CPU thread is actually not allowed and will cause a deadlock instead of the intended behavior. I don't believe there is anything on a real console that would stop you from executing code at address 0 (as long as the MMU has been set up to allow it), and Jit64::DoJit doesn't contain any check like this, so let's remove the check.		2021-04-01 11:28:53 +02:00
..
Android	Merge pull request #9614 from JosJuice/okay-fine-i-give-in	2021-03-28 09:29:08 -04:00
Core	JitArm64: Allow DoJit at address 0 (fix launching Wii titles)	2021-04-01 11:28:53 +02:00
DSPSpy	DSPSpy: sync Makefile with current devkitPro template	2020-06-08 04:21:41 +01:00
DSPTool	msbuild: bundle all dolphin "core" code into single library	2021-01-27 14:29:49 -08:00
PCH	msvc: bump _MSC_FULL_VER check to 192829335	2021-01-09 19:21:03 -08:00
UnitTests	Refactor CP array constants slightly	2021-03-26 17:27:21 -07:00
VSProps	msbuild: re-enable HAS_OPENGL and HAS_VULKAN	2021-01-27 19:10:53 -08:00
.clang-format
CMakeLists.txt	CMake: Build with -std:c++latest for MSVC	2021-03-03 23:44:35 +01:00
dolphin-emu.sln	msbuild: bundle all dolphin "core" code into single library	2021-01-27 14:29:49 -08:00