diff options
| author | Léo Lam <leo@leolam.fr> | 2020-11-28 21:09:26 +0100 |
|---|---|---|
| committer | Léo Lam <leo@leolam.fr> | 2020-11-28 21:11:27 +0100 |
| commit | c0f7f91507cad62d893b796121f1898859fb7c3b (patch) | |
| tree | 4052096b5e14f2b2d9588101fe1f16991b060e1b /Source/Core/VideoBackends/Vulkan/ObjectCache.cpp | |
| parent | a9845e0a3dbb2506742c8af9e332f380448ee02d (diff) | |
Core: Fix an assertion that mistakenly uses a fmt format string
Unfortunately, adding a DEBUG_ASSERT_MSG_FMT isn't actually possible
right now because of compiler bugs:
https://github.com/dolphin-emu/dolphin/pull/9284
We could require a newer version of GCC (10) but that would require
updating GCC on the build machines.
For what it's worth, older versions of GCC (8, 9) are broken in
many ways: adding constexpr to some Matrix functions causes GCC 8
to generate bugged code that causes the Wii IR pointer to disappear,
which means that the generated builds are already unusable
(see https://dolp.in/i12324).
Additionally, we've already had to add workarounds for those versions
in the format macros to fix compilation bugs. This time, it looks like
workarounds won't cut it; even applying the workaround
described in https://github.com/fmtlib/fmt/pull/1580 does not help.
Diffstat (limited to 'Source/Core/VideoBackends/Vulkan/ObjectCache.cpp')
0 files changed, 0 insertions, 0 deletions
