| Age | Commit message (Collapse) | Author |
|
|
|
We can iterate through the AdvancedGraphics settings and generate the UI
during runtime. This doesn't help runtime efficiency, but it helps a ton
in reducing the amount of work a developer needs in order to add a new
setting.
|
|
core: Fix MSVC errors
|
|
Just puts them all neatly into one place.
|
|
service: nfc: Update Implementation to match with latest RE
|
|
general: Silence -Wshadow{,-uncaptured-local} warnings
|
|
Mark SetIdleTimeDetectionExtension logging as debug
|
|
These occur in the latest commits in LLVM Clang.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Implement SSL service
|
|
There are still some other issues not addressed here, but it's a start.
Workarounds for false-positive reports:
- `RasterizerAccelerated`: Put a gigantic array behind a `unique_ptr`,
because UBSan has a [hardcoded limit](https://stackoverflow.com/questions/64531383/c-runtime-error-using-fsanitize-undefined-object-has-a-possibly-invalid-vp)
of how big it thinks objects can be, specifically when dealing with
offset-to-top values used with multiple inheritance. Hopefully this
doesn't have a performance impact.
- `QueryCacheBase::QueryCacheBase`: Avoid an operation that UBSan thinks
is UB even though it at least arguably isn't. See the link in the
comment for more information.
Fixes for correct reports:
- `PageTable`, `Memory`: Use `uintptr_t` values instead of pointers to
avoid UB from pointer overflow (when pointer arithmetic wraps around
the address space).
- `KScheduler::Reload`: `thread->GetOwnerProcess()` can be `nullptr`;
avoid calling methods on it in this case. (The existing code returns
a garbage reference to a field, which is then passed into
`LoadWatchpointArray`, and apparently it's never used, so it's
harmless in practice but still triggers UBSan.)
- `KAutoObject::Close`: This function calls `this->Destroy()`, which
overwrites the beginning of the object with junk (specifically a free
list pointer). Then it calls `this->UnregisterWithKernel()`. UBSan
complains about a type mismatch because the vtable has been
overwritten, and I believe this is indeed UB. `UnregisterWithKernel`
also loads `m_kernel` from the 'freed' object, which seems to be
technically safe (the overwriting doesn't extend as far as that
field), but seems dubious. Switch to a `static` method and load
`m_kernel` in advance.
|
|
|
|
|
|
|
|
k_server_session: translate special header for non-HLE requests
|
|
Use spans over guest memory where possible instead of copying data
|
|
|
|
|
|
|
|
|
|
|
|
core_timing: Remove GetCurrentTimerResolution in CoreTiming loop
|
|
kernel: Synchronize
|
|
Other programs may change this value, but if thousands of syscalls in this loop is undesirable, then we can just set this once.
|
|
Memory Tracking: Add mechanism to register small writes when gpu page is contested by GPU
|
|
fsmitm_romfsbuild: avoid full path lookups
|
|
|
|
|
|
- Address PR feedback.
- Add SecureTransport backend for macOS.
|
|
|
|
|
|
|
|
|
|
|
|
with the host GPU
|
|
|
|
|
|
|
|
|
|
|
|
|
|
I did test this beforehand, but not on MinGW, and the error that showed
up on the msvc builder didn't happen for me...
|
|
Turns out changes were needed after all.
|
|
- Add missing virtual destructor on `SSLBackend`.
- On Windows, filter out `POLLWRBAND` (one of the new flags added) when
calling `WSAPoll`, because despite the constant being defined on
Windows, passing it calls `WSAPoll` to yield `EINVAL`.
- Reduce OpenSSL version requirement to satisfy CI; I haven't tested
whether it actually builds (or runs) against 1.1.1, but if not, I'll
figure it out.
- Change an instance of memcpy to memmove, even though the arguments
cannot overlap, to avoid a [strange GCC
error](https://github.com/yuzu-emu/yuzu/pull/10912#issuecomment-1606283351).
|
|
The original name `larg` was copied from the OpenSSL documentation and
is not a typo of 'large' but rather an abbreviation of '`long`
argument'. But whatever, no harm in adding an underscore.
|