On DragonFly and NetBSD build fails with

src/common/virtual_buffer.cpp
src/common/virtual_buffer.cpp:16:10: fatal error: sys/sysinfo.h: No such file or directory
 #include <sys/sysinfo.h>
          ^~~~~~~~~~~~~~~

buffer_queue: Make use of designated initializers/std::nullopt where applicable

CMakeLists: Resolve #4478

common/atomic_ops: Don't cast away volatile from pointers

loader: Make IdentifyFile typesafe

time_zone_binary: Make use of designated initializers

vi: IApplicationDisplayService:GetIndirectLayerImageRequiredMemoryInfo

hle: nvdrv: Rewrite of GPU memory management.

CMakeLists: Update several libraries

renderer_opengl: Use 1/4 of all threads for async shader compilation

game_list_worker: Fix game list subdirectory scanning

perf_stats: Mark GetMeanFrametime() as const 

vk_texture_cache: Silence -Wmissing-field-initializer warnings

patch_manager: Resolve -Wignored-qualifier warnings

yuzu: Resolve C++20 deprecation warnings related to lambda captures

profile_manager: Make use of designated initializers 

dmnt_cheat_vm: Make use of designated initializers

fsp-srv: Stub Read/WriteSaveDataFileSystemExtraDataWithMaskBySaveDataAttribute

tests/core_timing: Remove pragma optimize(off)

service/ldr: Resolve sign mismatch warnings

registered_cache: Resolve -Wmaybe_uninitialized warnings

sm: Make use of IsBaseOf for GetService

Same behavior, but allows us to avoid a now-unnecessary zero
initialization.

The general pattern is to mark mutexes as mutable when it comes to
matters of constness, given the mutex acts as a transient member of a
data structure.

C++20 deprecates capturing the this pointer via the '=' capture.
Instead, we replace it or extend the capture specification.

We were performing an int < size_t comparison. We can just correct the
type of the induction variable.

This switch is enabled by default in all recent versions of GCC and
Clang.

I made a review comment about this in the PR that this was introduced
in (#3955, commit 71c47792), but it
seems to have been missed.

We shouldn't be using this pragma here because it's MSVC specific. This
causes warnings on other compilers.

The test it's surrounding is *extremely* dubious, but for the sake of
silencing warnings on other compilers, we can mark "placebo" as volatile
and be on with it.

file_sys/mode: Make use of DECLARE_ENUM_FLAG_OPERATORS with Mode

Allows compilers to eliminate unnecessary zeroing out of the optional's
buffer.

Allows some implementations to completely avoid unnecessarily zeroing
out the internal buffer.

More compact code.

Allows for more compact code.

Same behavior, minus a hand-rolled operator.

Top level const will always be ignored in this case, so it can be
removed.

While we're at it, we can avoid a redundant map lookup.