This is a bounds check to ensure that the thread priority is within the
valid range of 0-64. If it exceeds 64, that doesn't necessarily mean
that an actual priority of 64 was expected (it actually means whoever
called the function screwed up their math).

Instead clarify the message to indicate the allowed range of thread
priorities.

Now that we handle the kernel capability descriptors we can correct
CreateThread to properly check against the core and priority masks
like the actual kernel does.

Makes them consistent with their kernel capability counterparts.

Rather than use a switch here, this can be collapsed into a simple range
check, which is a little easier on the eyes.

kernel/process: Start the main thread using the specified ideal core

Print backtrace on svcBreak

service/time: Minor cleanup

Moves some variables closer to their actual usage sites.

gpu: Remove PixelFormat G8R8U and G8R8S, as they do not seem to exist.

- Fixes UI rendering issues in The Legend of Zelda: Breath of the Wild.

audio_core: Convert LOG_CRITICAL + UNREACHABLE over to UNIMPLEMENTED/UNIMPLEMENTED_MSG

These two macros being used in tandem were used prior to the
introduction of UNIMPLEMENTED and UNIMPLEMENTED_MSG. This provides
equivalent behavior, just with less typing/reading involved.

This matches kernel behavior in that processes are started using their
specified ideal core, rather than always starting on core 0.

This makes the naming more closely match its meaning. It's just a
preferred core, not a required default core. This also makes the usages
of this term consistent across the thread and process implementations.

This function isn't a general purpose function that should be exposed to
everything, given it's specific to initializing the main thread for a
Process instance.

Given that, it's a tad bit more sensible to place this within
process.cpp, which keeps it visible only to the code that actually needs
it.

file_sys/program_metadata: Print out more descriptive address space descriptions

kernel/process: Remove most allocation functions from Process' interface

Provides extra information that makes it easier to tell if an executable
being run is using a 36-bit address space or a 39-bit address space.
While we don't support AArch32 executables yet, this also puts in
distinguishing information for the 32-bit address space types as well.

In all cases that these functions are needed, the VMManager can just be
retrieved and used instead of providing the same functions in Process'
interface.

This also makes it a little nicer dependency-wise, since it gets rid of
cases where the VMManager interface was being used, and then switched
over to using the interface for a Process instance. Instead, it makes
all accesses uniform and uses the VMManager instance for all necessary
tasks.

All the basic memory mapping functions did was forward to the Process'
VMManager instance anyways.

Add missing uintBitsToFloat to SetRegisterToHalfFloat

kernel: Handle kernel capability descriptors

Improve Zero flag implementation

hid: Fix SetNpadJoyHoldType and improve logging.

npad: Remove code to invert input in horizontal mode.

kernel/vm_manager: Reset region attributes when unmapping a VMA

am: Implement GetSaveDataSize and ExtendSaveData using files

These functions come in a pair and are needed by Smash Ultimate, Minecraft, and Skyrim, amongst others.

This stores a file in the save directory called '.yuzu_save_size' which stores the two save sizes (normal area and journaled area) sequentially as u64s.

Serves no actual purpose in this instance besides making NACP's copy assignment deleted, which is not intended behavior.

Allows these functions to compile when T is not u8.

renderer_opengl: Correct forward declaration of FramebufferLayout

configure_per_general: Mark UI strings as translatable in the constructor

Like the other members related to memory regions, the attributes need to
be reset back to their defaults as well.

configure_input_simple: Make input profile array constexpr