Browse Source
memory: Dehardcode the use of fixed memory range constants
memory: Dehardcode the use of fixed memory range constants
The locations of these can actually vary depending on the address space layout, so we shouldn't be using these when determining where to map memory or be using them as offsets for calculations. This keeps all the memory ranges flexible and malleable based off of the virtual memory manager instance state.nce_cpp
11 changed files with 60 additions and 75 deletions
-
15src/core/gdbstub/gdbstub.cpp
-
20src/core/hle/kernel/process.cpp
-
4src/core/hle/kernel/shared_memory.cpp
-
3src/core/hle/kernel/svc.cpp
-
3src/core/hle/kernel/thread.cpp
-
7src/core/loader/deconstructed_rom_directory.cpp
-
24src/core/loader/elf.cpp
-
7src/core/loader/nro.cpp
-
9src/core/loader/nso.cpp
-
12src/core/memory.cpp
-
31src/core/memory.h
Write
Preview
Loading…
Cancel
Save
Reference in new issue