| Age | Commit message (Collapse) | Author |
|---|
|
common/file_util: Allow access to files on network shares
|
|
file_util: Early-exit in WriteArray and ReadArray if specified lengths are zero
|
|
|
|
|
|
|
|
|
|
|
|
It's undefined behavior to pass a null pointer to std::fread and
std::fwrite, even if the length passed in is zero, so we must perform
the precondition checking ourselves.
A common case where this can occur is when passing in the data of an
empty std::vector and size, as an empty vector will typically have a
null internal buffer.
While we're at it, we can move the implementation out of line and add
debug checks against passing in nullptr to std::fread and std::fwrite.
|
|
yuzu: Drop SDL2 and Qt frontend Vulkan requirements
|
|
On Windows, network shares use paths like \\server\share\file which were
being broken by FileUtil::SanitizePath() removing double slashes.
Changed the code in SanitizePath to permit a double-backslash if it
occurs at the start of a filepath (on Windows only).
|
|
|
|
* IOFile: Make the move constructor and move assignment operator noexcept
Certain parts of the standard library try to determine whether or not a
transfer operation should either be a copy or a move. The prevalent notion
of move constructors/assignment operators is that they should not throw,
they simply move an already existing resource somewhere else.
This is typically done with 'std::move_if_noexcept'. Like the name says,
if a type's move constructor is noexcept, then the functions retrieves an
r-value reference (for move semantics), or an l-value (for copy semantics)
if it is not noexcept.
As IOFile deletes the copy constructor and copy assignment operators,
using IOFile with certain parts of the standard library can fail in
unexcepted ways (especially when used with various container
implementations). This prevents that.
* fix various instances of -1 being assigned to unsigned types
* do not assign in conditional statements
* File/IOFile: Check _tfopen_s properly
* common/file_util.cpp: address review comments
Co-authored-by: Lioncash <mathew1800@gmail.com>
Co-authored-by: Shawn Hoffman <godisgovernment@gmail.com>
Co-authored-by: Sepalani <sepalani@hotmail.fr>
|
|
PageTable: move backing addresses to a children class as the CPU page table does not need them.
|
|
does not need them.
This PR aims to reduce the memory usage in the CPU page table by moving
GPU specific parameters into a child class. This saves 1Gb of Memory for
most games.
|
|
|
|
|
|
Instead of pre-specializing shaders and then post-specializing them,
drop the later and only "specialize" the shader while decoding it.
|
|
|
|
Port citra-emu/citra#5039: "common/logging: don't use regex for path trimming"
|
|
|
|
|
|
An implementation of the cemuhook motion/touch protocol, this adds the
ability for users to connect several different devices to citra to send
direct motion and touch data to citra.
Co-Authored-By: jroweboy <jroweboy@gmail.com>
|
|
The information is duplicated in the brand string and the telemetry field is unused
|
|
|
|
|
|
|
|
We relies on UNREACHABLE's noreturn attribute to eliminate parent's "no return value" warning. However, this was wrapped in a `if(!false)` block, which compilers may not unfold to recognize the noreturn nature.
|
|
|
|
Makes code that uses the macros consistent by requiring the lines to be
terminated with a semicolon.
|
|
This is unused, so it can be removed. There's better ways of ensuring
zeroed out padding bits, like using zero-initialization, anyhow.
|
|
We can trivially resolve these by casting the characters to unsigned
values and then shifting the bits.
|
|
|
|
- Zero initialization here is useful for determinism.
|
|
See bunneis comment here https://github.com/citra-emu/citra/pull/4629#discussion_r258533167.
They were supposed to be removed by him, but he missed them.
|
|
Kernel: Implement a New Thread Scheduler V2
|
|
|
|
ConstBufferLocker class to shaders.
|
|
Makes it explicit that the header is intended for iterator-based
algorithms that can ideally operate on any type.
|
|
Makes the header more general for other potential algorithms in the
future. While we're at it, include a missing <functional> include to
satisfy the use of std::less.
|
|
|
|
This was related to the source allocator being passed into the
constructor potentially having a different type than allocator being
constructed.
We simply need to provide a constructor to handle this case.
This resolves issues related to the allocator causing debug builds on
MSVC to fail.
|
|
Allows containers and other data structures to consider optimizations
based off of them. We satisfy all of these requirements anyways.
|
|
Silence miscellaneous warnings
|
|
ci: Add custom titlebars for mainline and patreon
|
|
|
|
|
|
modes.
|
|
|
|
|
|
This is better than just using something like Common.Filesystem or Common.Memory
|
