| Age | Commit message (Collapse) | Author |
|---|
|
- Used by Undertale.
|
|
- Used by Undertale.
|
|
This is inconsistent with our coding style.
|
|
Implemented Fast Layered Copy
|
|
common: Remove bit_set.h
|
|
|
|
kernel/handle_table: Minor changes
|
|
While admirable as a means to ensure immutability, this has the
unfortunate downside of making the class non-movable. std::move cannot
actually perform a move operation if the provided operand has const data
members (std::move acts as an operation to "slide" resources out of an
object instance). Given Barrier contains move-only types such as
std::mutex, this can lead to confusing error messages if an object ever
contained a Barrier instance and said object was attempted to be moved.
|
|
Simplifies the constructor interfaces for Barrier and Event classes.
|
|
Keeps the non-member interface in one spot instead of split into two
places, making it nicer to locate functions.
|
|
This is also unused and superceded by standard functionality. The
standard library provides std::this_thread::sleep_for(), which provides
a much more flexible interface, as different time units can be used with
it.
|
|
This is an old function that's no longer necessary. C++11 introduced
proper threading support to the language and a thread ID can be
retrieved via std::this_thread::get_id() if it's ever needed.
|
|
This is an analog of BitSet from Dolphin that was introduced to allow
iterating over a set of bits. Given it's currently unused, and given
that std::bitset exists, we can remove this. If it's ever needed in the
future it can be brought back.
|
|
This will log all data it receives, log all calls to its methods and push dummy data into both channels on execution.
|
|
|
|
|
|
when docked mode is enable
|
|
|
|
These don't depend on class state, and are effectively implementation
details, so they can go into the cpp file .
|
|
The previous handle table size is a holdover from Citra. The actual
handle table construct on Horizon only allows for a maximum of 1024
entries.
|
|
We don't need to potentially inline the teardown logic of all of the
handle instances.
|
|
Use default values for unknown framebuffer pixel format
|
|
gl_shader_decompiler: Use UNIMPLEMENTED when applicable
|
|
|
|
am/applets: Minor cleanup
|
|
|
|
- Used by Undertale.
|
|
gl_shader_decompiler: Remove UNREACHABLE when setting RZ
|
|
common/math_util: Minor cleanup
|
|
|
|
|
|
|
|
Xbyak is currently entirely unused. Rather than carting it along, remove
it and get rid of a dependency. If it's ever needed in the future, then
it can be re-added (and likely be more up to date at that point in
time).
|
|
|
|
Gets rid of the need to use typename to access the ::type alias.
|
|
Allows objects that contain rectangle instances to be constexpr
constructible as well.
|
|
const/constexpr variables have internal linkage by default.
|
|
This hasn't been used since the project started, so we may as well get
rid of it to keep it from bit rotting.
|
|
maxwell_3d: Initialize rasterizer color mask registers as enabled.
|
|
|
|
applicable
|
|
- Fixes rendering regression with Sonic Mania.
|
|
The interface for shared memory was changed, but another commit was
merged that relied on the (previously public) internals of SharedMemory.
This amends that discrepancy.
|
|
The decision was made to name them LayeredExeFS instead of just LayeredFS to differentiate from normal RomFS-based mods. The name may be long/unweildy, but conveys the meaning well.
|
|
kernel/shared_memory: Make data members private, plus minor interface changes
|
|
ldr: Clean up error codes
|
|
kernel/process: Move <random> include to the cpp file
|
|
common/assert: Make the UNIMPLEMENTED macro properly assert
|
|
Fills out the struct according to information provided by SwitchBrew
|
|
assertions
Currently, there's no way to specify if an assertion should
conditionally occur due to unimplemented behavior. This is useful when
something is only partially implemented (e.g. due to ongoing RE work).
In particular, this would be useful within the graphics code.
The rationale behind this is it allows a dev to disable unimplemented
feature assertions (which can occur in an unrelated work area), while
still enabling regular assertions, which act as behavior guards for
conditions or states which must not occur. Previously, the only way a
dev could temporarily disable asserts, was to disable the regular
assertion macros, which has the downside of also disabling, well, the
regular assertions which hold more sanitizing value, as opposed to
unimplemented feature assertions.
|
