Tree:
527f634966
2ndAdjustmentAndroid
2ndAdjustmentVulkan
2ndAdjustmentVulkanV3-STOP_FORCE_PUSHING_CAMILLE
2ndAdjustmentVulkanv2
2ndgpuopts
Kernel
Update-some-barriers-test
astc_optimization1
astc_optimizations
atomicops-mxwell
bcn-ternary-soft
bioshock
bump-httplib-minver
civa
descriptor
descriptor_pool_opt
descriptor_set
discfix
dmnt2
drop-msvc
dynarmic
dynarmic-ppc64
eden-managarm
eden-orbis-ps4
eds-true-adreno-fixes
eds-true-adreno-fixes-pre-0.1.0
eds_changes1
eds_changes_phasewise
feat/android_kotlin_compose
feat/game_override
fix-friend-list-freeze
fix-grid-autoalign
fix-update-android
fix/discord-rpc
flatopsfixes23485
fs-try
gpuopts
kosmic_krisp
kosmickrisp
lanobu
lines
liz-dynarmic-macos-fbsd-port
liz-heaptrack-fix
lizize/fixcrashwehenimagesizeexceed
lizzie/adreno5-mali-driver-fix
lizzie/anv-cached-mesa-hack
lizzie/astc-mp4-improv
lizzie/bsdsockets-mod-fix
lizzie/bundleevil123
lizzie/civ7-y2k-dns-ban
lizzie/controller7547
lizzie/cpudetect1234
lizzie/demangle-cxxabi
lizzie/dynarmic-exclusive-fixups
lizzie/dynarmic-experiment-inline-matchers
lizzie/dynarmic-faster-xbyak
lizzie/edit-handheld-mode
lizzie/evil-f32-u32-format-fix
lizzie/evil-meow-meow
lizzie/fbsd-shm_create_largepage
lizzie/ffmpeg-d1d873c003
lizzie/fix-nvmap-handles
lizzie/fix-nvmap-handles-but-evil
lizzie/fixandroid7435683485
lizzie/forceattachements-at-all-times
lizzie/fs-msvc-succks
lizzie/fsfix12
lizzie/giudolyfix
lizzie/gutter-sw-blitter
lizzie/hleinlineremoveredundant
lizzie/inline-123
lizzie/inline-cmif-request
lizzie/inline-gpu-works1
lizzie/inlinecodecnvenc
lizzie/invert-gyro
lizzie/ios-port-sud
lizzie/jit-addresschecks
lizzie/ltofix123
lizzie/macos-network-ifaces
lizzie/macos-vk-metal-fix-stype
lizzie/maxwell-dumb-tools
lizzie/mboverhead1
lizzie/mlp223
lizzie/multicore-macos-fix1
lizzie/nce-invalidate-split
lizzie/nce-port1123
lizzie/noexcept-dynarmic
lizzie/nx-tzdb-meowed
lizzie/powerunswizzle
lizzie/product-model-wawa
lizzie/readonly-listicons
lizzie/remove-disassembler-dynarmic
lizzie/remove-logging-thread
lizzie/remove-mlp-2-level
lizzie/restore-fcsm
lizzie/rework-ips
lizzie/sdsize-persiz
lizzie/settings-blocked-domains
lizzie/sgsr
lizzie/simplify-invalid-acc
lizzie/sm-AtmosphereHasService
lizzie/splay
lizzie/stable-shader-pools
lizzie/stuff-for-fun-but-evil
lizzie/stupid-socket-bullshit
lizzie/sysarchive7543
lizzie/tls-codegen123
lizzie/ulaunch-attempt1
lizzie/unaligned-attempt-2
lizzie/unity-build
lizzie/update-faq-link-wwa
lizzie/vk-ext-fault-info
lizzie/vkexperiments1-highp-fucked
lizzie/wallclock-remove-indirection1
lizzie/wstring-uni-123
lizzie/xbyak-force-bundled
lizzie/xcode-evil-shit-123
macroify-surface-stuffs
many/fix-tomodachi
master
memory_changes
mmap-fixews
mutliplayer-filter-better1
n64
nce_cpp
pipelinederivative
qcomopts2
qml-reorg
queries
querybugfix
refactoreds2
release-early-fences
release/0.0.3
release/0.0.4
release/0.1.0
revert-2695
showcase
showcase2
sjkdbsdfjkbsdf-2834
spvopts
sured-revert
techno48473719
test-revert-gpu-optim
test2
tex_opt
true-eds
true-eds-graphics
true-eds-pre-0.0.1
uma
update-deps-040626
update-translations-1777730513
vk-fix-oom-force-maller-buffers
vk-symph
vkexperiments1
vuid00336_1
vuid02999
vuid04553
vulkanasync
workgroup
xbzk-dma-pusher-step-redesign
xbzk-saf-recursive-write-with-permission-request
xbzk/background-support
xbzk/flicker-fix
xbzk/unreal-unsafe-junk-guards
xbzk/vulkan-vuid-goodies-pack
0.0.0
0.0.1-pre-alpha
0.0.2-pre-alpha
test-tag1
test-tag2
v0.0.3
v0.0.3-rc1
v0.0.3-rc2
v0.0.3-rc3
v0.0.3.git
v0.0.4
v0.0.4-rc1
v0.0.4-rc2
v0.0.4-rc2.test
v0.0.4-rc2.test2
v0.0.4-rc3
v0.0.4-rc3.test1
v0.0.4-rc3.test2
v0.0.4.test
v0.1.0
v0.1.0-rc1
v0.1.1
v0.2.0-rc1
v0.2.0-rc2
${ noResults }
5 Commits (527f6349660c21039f7757312784601e4a8e0c6d)
| Author | SHA1 | Message | Date |
|---|---|---|---|
|
|
1d2de5c4b5 |
core_timing: Rename CoreTiming namespace to Core::Timing
Places all of the timing-related functionality under the existing Core namespace to keep things consistent, rather than having the timing utilities sitting in its own completely separate namespace. |
7 years ago |
|
|
5ae0d6cba2 |
Changed logging to be "Log before execution", Added more error logging, all services should now log on some level
|
8 years ago |
|
|
11a9e90d8d |
Stubbed IRS (#1349)
* Stubbed IRS Currently we have no ideal way of implementing IRS. For the time being we should have the functions stubbed until we come up with a way to emulate IRS properly. * Added IRS to logging backend * Forward declared shared memory for irs |
8 years ago |
|
|
8a9b062587 |
hle/service: Default constructors and destructors in the cpp file where applicable
When a destructor isn't defaulted into a cpp file, it can cause the use
of forward declarations to seemingly fail to compile for non-obvious
reasons. It also allows inlining of the construction/destruction logic
all over the place where a constructor or destructor is invoked, which
can lead to code bloat. This isn't so much a worry here, given the
services won't be created and destroyed frequently.
The cause of the above mentioned non-obvious errors can be demonstrated
as follows:
------- Demonstrative example, if you know how the described error happens, skip forwards -------
Assume we have the following in the header, which we'll call "thing.h":
\#include <memory>
// Forward declaration. For example purposes, assume the definition
// of Object is in some header named "object.h"
class Object;
class Thing {
public:
// assume no constructors or destructors are specified here,
// or the constructors/destructors are defined as:
//
// Thing() = default;
// ~Thing() = default;
//
// ... Some interface member functions would be defined here
private:
std::shared_ptr<Object> obj;
};
If this header is included in a cpp file, (which we'll call "main.cpp"),
this will result in a compilation error, because even though no
destructor is specified, the destructor will still need to be generated by
the compiler because std::shared_ptr's destructor is *not* trivial (in
other words, it does something other than nothing), as std::shared_ptr's
destructor needs to do two things:
1. Decrement the shared reference count of the object being pointed to,
and if the reference count decrements to zero,
2. Free the Object instance's memory (aka deallocate the memory it's
pointing to).
And so the compiler generates the code for the destructor doing this inside main.cpp.
Now, keep in mind, the Object forward declaration is not a complete type. All it
does is tell the compiler "a type named Object exists" and allows us to
use the name in certain situations to avoid a header dependency. So the
compiler needs to generate destruction code for Object, but the compiler
doesn't know *how* to destruct it. A forward declaration doesn't tell
the compiler anything about Object's constructor or destructor. So, the
compiler will issue an error in this case because it's undefined
behavior to try and deallocate (or construct) an incomplete type and
std::shared_ptr and std::unique_ptr make sure this isn't the case
internally.
Now, if we had defaulted the destructor in "thing.cpp", where we also
include "object.h", this would never be an issue, as the destructor
would only have its code generated in one place, and it would be in a
place where the full class definition of Object would be visible to the
compiler.
---------------------- End example ----------------------------
Given these service classes are more than certainly going to change in
the future, this defaults the constructors and destructors into the
relevant cpp files to make the construction and destruction of all of
the services consistent and unlikely to run into cases where forward
declarations are indirectly causing compilation errors. It also has the
plus of avoiding the need to rebuild several services if destruction
logic changes, since it would only be necessary to recompile the single
cpp file.
|
8 years ago |
|
|
8724896db5 |
service/hid: Add irs services
|
8 years ago |