| Age | Commit message (Collapse) | Author |
|---|
|
* Implemented the puller semaphore operations.
* Nit: Fix 2 style issues
* Nit: Add Break to default case.
* Fix style.
* Update for comments. Added ReferenceCount method
* Forgot to remove GpuSmaphoreAddress union.
* Fix the clang-format issues.
* More clang formatting.
* two more white spaces for the Clang formatting.
* Move puller members into the regs union
* Updated to use Memory::WriteBlock instead of Memory::Write*
* Fix clang style issues
* White space clang error
* Removing unused funcitons and other pr comment
* Removing unused funcitons and other pr comment
* More union magic for setting regs value.
* union magic refcnt as well
* Remove local var
* Set up the regs and regs_assert_positions up properly
* Fix clang error
|
|
|
|
This is kind of a large hole in the API, given we allow popping signed
values. This fixes that.
|
|
video_core/shader: Minor changes
|
|
This quite literally functions as a basic setter. No other error
checking or anything (since there's nothing to really check against).
With this, it completes the pm:bm interface in terms of functionality.
|
|
Just minor tidying of interfaces.
|
|
This appears to be a vestigial API function that's only kept around for
compatibility's sake, given the function only returns a success error
code and exits.
Since that's the case, we can remove the stubbed notification from the
log, since doing nothing is technically the correct behavior in this
case.
|
|
Given we're in the area, these are three trivial typos that can be
corrected.
|
|
Orders the class members in the same order that they would actually be
initialized in. Gets rid of two compiler warnings.
|
|
std::moveing a local variable in a return statement has the potential to
prevent copy elision from occurring, so this can just be converted into
a regular return.
|
|
kernel/svc: Log out uncaught C++ exceptions from svcBreak
|
|
video_core: Silent implicit conversion warning
|
|
Looking into the implementation of the C++ standard facilities that seem
to be within all modules, it appears that they use 7 as a break reason
to indicate an uncaught C++ exception.
This was primarily found via the third last function called within
Horizon's equivalent of libcxxabi's demangling_terminate_handler(),
which passes the value 0x80000007 to svcBreak.
|
|
According to documentation, if the argument of std::exp is zero, one is returned.
However we want the return value to be also zero in this case so no audio is played.
|
|
|
|
video_core: Replace gl_shader_decompiler with an IR based decompiler
|
|
frontend: Refactor ScopeAcquireWindowContext out of renderer_opengl.
|
|
|
|
|
|
Commercial games assume that this value is 1 but they never set it. On
the other hand nouveau manually sets this register. On
ConfigureFramebuffers we were asserting for what we are actually
implementing (according to envytools).
|
|
yuzu/configuration: Remove unnecessary inclusions where applicable
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
QT Frontend: Add a Loading screen with progressbar
|
|
gl_rasterizer_cache: Use dirty flags for framebuffers
|
|
gl_rasterizer: Use DSA for VAOs and buffers
|
|
yuzu/configuration/configure_web: Amend verification string
|
|
loader: Add getters for application banner and logo
|
|
|
|
With shader caches on the horizon, one requirement is to provide visible
feedback for the progress. The shader cache reportedly takes several
minutes to load for large caches that were invalidated, and as such we
should provide a loading screen with progress.
Adds a loading screen widget that will be shown until the first frame of
the game is swapped. This was chosen in case shader caches are not being
used, several games still take more than a few seconds to launch and
could benefit from a loading screen.
|
|
yuzu/web_browser: Minor cleanup
|
|
gl_rasterizer: Silent unsafe mix warning
|
|
This isn't used at all, so we can just get rid of it.
|
|
|
|
applicable
Allows removing the inclusion of the main input common header from the
UI config header.
|
|
inclusions
|
|
|
|
|
|
|
|
'this' isn't actually used within the lambda, since what we need
from the class is already assigned within the capture section of
the lambda.
|
|
It's a common UI pattern to use an ellipsis to indicate an ongoing
action, rather than just specifying the word by itself.
|
