There was an error fetching the commit references. Please try again later.
kernel/thread: Use a regular pointer for the owner/current process
There's no real need to use a shared pointer in these cases, and only makes object management more fragile in terms of how easy it would be to introduce cycles. Instead, just do the simple thing of using a regular pointer. Much of this is just a hold-over from citra anyways. It also doesn't make sense from a behavioral point of view for a process' thread to prolong the lifetime of the process itself (the process is supposed to own the thread, not the other way around).
Showing
- src/core/arm/dynarmic/arm_dynarmic.cpp 1 addition, 1 deletionsrc/core/arm/dynarmic/arm_dynarmic.cpp
- src/core/core.cpp 4 additions, 3 deletionssrc/core/core.cpp
- src/core/core.h 5 additions, 5 deletionssrc/core/core.h
- src/core/hle/kernel/kernel.cpp 6 additions, 6 deletionssrc/core/hle/kernel/kernel.cpp
- src/core/hle/kernel/kernel.h 5 additions, 5 deletionssrc/core/hle/kernel/kernel.h
- src/core/hle/kernel/scheduler.cpp 4 additions, 4 deletionssrc/core/hle/kernel/scheduler.cpp
- src/core/hle/kernel/svc.cpp 6 additions, 6 deletionssrc/core/hle/kernel/svc.cpp
- src/core/hle/kernel/thread.cpp 4 additions, 4 deletionssrc/core/hle/kernel/thread.cpp
- src/core/hle/kernel/thread.h 4 additions, 4 deletionssrc/core/hle/kernel/thread.h
- src/tests/core/arm/arm_test_common.cpp 2 additions, 1 deletionsrc/tests/core/arm/arm_test_common.cpp
Loading
Please register or sign in to comment