Port citra-emu/citra#4269: "OSX: Set MACOSX_DEPLOYMENT_TARGET to 10.13"

loader: Make the Load() function take a process as a regular reference, not a SharedPtr

A process should never require being reference counted in this
situation. If the handle to a process is freed before this function is
called, it's definitely a bug with our lifetime management, so we can
put the requirement in place for the API that the process must be a
valid instance.

Port citra-emu/citra#4258: "Meta: Add gitattributes file"

kernel/object: Remove unnecessary std::move from DynamicObjectCast()

video_core: Implement point_size and add point state sync

gl_state: Pack sampler bindings into a single ARB_multi_bind

process/vm_manager: Initial modifications to load NPDM metadata

boost::static_pointer_cast for boost::intrusive_ptr (what SharedPtr is),
takes its parameter by const reference. Given that, it means that this
std::move doesn't actually do anything other than obscure what the
function's actual behavior is, so we can remove this. To clarify, this
would only do something if the parameter was either taking its argument
by value, by non-const ref, or by rvalue-reference.

Port citra-emu/citra#3979 game_list: move SearchField to game_list_p.h and fix untranslated text

stream: Preserve enum class type in GetState()

FPCR register was uninitialized at start up

CMake: Remove superfluous CMAKE_RUNTIME_OUTPUT_DIRECTORY assignment

Improved Fast Swizzle and Legacy Swizzle

fsmitm_romfsbuild: Minor changes

Avoids making copies of large std::vector instances where it's trivially
avoidable to do so.

Theres no need to do explicit bitwise arithmetic here, when we have a
function that does this with a more descriptive name.

kernel/scheduler: Take ARM_Interface instances by reference

service: Add missing headers inclusions where applicable

video_core: Add asserts for CS, TFB and alpha testing

vfs: Minor cleanup related changes to layered VFS code

travis: Make macOS builds utilize Xcode 10

Avoids the need to nest code quite a bit by early-exiting in error
cases.

Add asserts for compute shader dispatching, transform feedback being
enabled and alpha testing. These have in common that they'll probably break
rendering without logging.

Orders the initializer list members to be in the same order that they
would be initialized in. Avoids compiler warnings.

Cast where explicitly necessary and in other cases we can simply modify
the algorithm to accomodate larger data.

fsmitm_romfsbuild: Remove unnecessary constructors and initializers for RomFSBuildFileContext and RomFSBuildDirectoryContext

There's no need to duplicate in-class initializers with a constructor
initializer list. std::strings also initialize to empty by default.

The std::vector instances are already initially allocated with all
entries having these values, there's no need to loop through and fill
them with it again when they aren't modified.

auto x = 0;

auto-deduces x to be an int. This is undesirable when working with
unsigned values. It also causes sign conversion warnings. Instead, we
can make it a proper unsigned value with the correct width that the
following expressions operate on.

Ternary operators have a lower precedence than arithmetic operators, so
what was actually occurring here is "return (out + full) ? x : y" which most
definitely isn't intended, given we calculate out recursively above. We
were essentially doing a lot of work for nothing.

This can cause warnings about static constructors, and is also not ideal
performance-wise due to the indirection through std::function. This also
keeps the behavior itself separate from the surrounding code, which can
make it nicer to read, due to the size of the code.

Given we just recently had a patch backport this from citra, let's try
and keep the convention uniform.

Given these are only added to the class to allow those functions to
access the private constructor, it's a better approach to just make them
static functions in the interface, to make the dependency explicit.

This converts it into a regular constructor parameter. There's no need
to make this a template parameter on the class when it functions
perfectly well as a constructor argument.

This also reduces the amount of code bloat produced by the compiler, as
it doesn't need to generate the same code for multiple different
instantiations of the same class type, but with a different fill value.