The JIT is mature enough that this setting can be removed, falling back
to Unicorn only on unsupported architectures. Any missing features from
Unicorn (of which there are extremely few), are mostly
developer-oriented, which most users don't care about.

Features should be coordinated with the JIT, not the interpreter,
anyhow.

This was initially necessary when AArch64 JIT emulation was in its
infancy and all memory-related instructions weren't implemented.

Given the JIT now has all of these facilities implemented, we can remove
these functions from the CPU interface.

Add Repository Sync Pipeline

gl_rasterizer: Amend documentation comment for ConfigureFramebuffers()

vk_scheduler: Drop execution context in favor of views

IFriendService::GetFriendList

pm: Implement various pm commands for finding process and title IDs

mii: Implement IDatabaseService SetInterfaceVersion

video_core: Add missing override specifiers

Add Pipeline Definitions for Azure CI

[skip ci]

We don't have any friends implemented in Yuzu yet so it doesn't make sense to return any friends. For now we'll be returning 0 friends however the information provided will allow a proper implementation of this cmd when needed.

must_reconfigure isn't a parameter for this function any more, so it can
be replaced with current_state.

While we're at it, we can make the parameters of the declaration match
the same name as the ones in the definition.

audren: Only manage wave buffers with a size

hid:StartLrAssignmentMode, hid:StopLrAssignmentMode, hid:SwapNpadAssignment

apm: Initial implementation of performance config and boost mode

fsp-srv: Implement Access Logging Functionality

Delete decode_integer_set.cpp

These are no longer used within this header, so they can be removed.

Instead of passing by copy an execution context through out the whole
Vulkan call hierarchy, use a command buffer view and fence view
approach.

This internally dereferences the command buffer or fence forcing the
user to be unable to use an outdated version of it on normal usage.
It is still possible to keep store an outdated if it is casted to
VKFence& or vk::CommandBuffer.

While changing this file, add an extra parameter for Flush and Finish to
allow releasing the fence from this calls.

Appears to set a member variable used to affect the API that games access, and the method used to store data.

core/reporter: Minor changes

 kernel/vm_manager: Handle stack/TLS IO region placement a little better 

am: Implement GetAccumulatedSuspendedTickValue

These aren't used within the central memory management code, so they can
be removed.

This isn't used by anything in the header file, so it can be removed.

Provides a more accurate name for the memory region and also
disambiguates between the map and new map regions of memory, making it
easier to understand.

Handles the placement of the stack a little nicer compared to the
previous code, which was off in a few ways. e.g.

The stack (new map) region, shouldn't be the width of the entire address
space if the size of the region calculation ends up being zero. It
should be placed at the same location as the TLS IO region and also have
the same size.

In the event the TLS IO region contains a size of zero, we should also
be doing the same thing. This fixes our memory layout a little bit and
also resolves some cases where assertions can trigger due to the memory
layout being incorrect.

Taking the json instance as a constant reference, makes all moves into
the parameter non-functional, resulting in copies. Taking it by value
allows moves to function.

Adds missing inclusions to prevent potential compilation issues.

The Reporter class is part of the Core namespace, so the System class
doesn't need to be qualified.

This can inhibit copy-elision, so we can remove this redundant move.