You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there a genuine need to use Boost’s flat_map here, as opposed to just std::map?
Performance-wise it doesn’t seem to matter in practice which implementation is used, so even if this is just a bug in either GCC or Boost, I would suggest replacing it.
…tingTools#252)
I do not see a reason to prefer the flat_map implementation,
and it’s causing crashes when compiled with GCC >= 13 and
Boost 1.85.0 at optimization level 2 or higher.
Whether or not this is a bug in GCC, or Boost hitting a case of
undefined behavior, avoiding it altogether doesn’t seem to hurt.
Fixesarch1t3cht#137
Co-authored-by: Mia Herkt <[email protected]>
When building with Boost 1.85.0 and GCC >= 13 with optimization level 2 or greater, Aegisub as well as the thesaurus test case crash here:
Aegisub/libaegisub/common/thesaurus.cpp
Line 48 in 80491ba
The same does not occur with Clang 18 or lower optimization levels, so this might be a GCC bug.
System is openSUSE Tumbleweed 20240524.
Backtrace:
The text was updated successfully, but these errors were encountered: