https://gcc.gnu.org/bugzilla/show_bug.cgi?id=128270
--- Comment #8 from Aliaksei Kandratsenka <alkondratenko at gmail dot com> --- Thanks a lot! That was a much faster turnaround than I expected (e.g., I've run into more CFI issues with Clang and haven't had much luck getting upstream traction on them). For context, testing for aw-backtrace involved single-stepping through code, verifying backtraces at every instruction, and running static analysis. While not a bulletproof guarantee, GCC (at least on x86-64) has shown no CFI bugs so far other than this one. (I had incorrectly assumed this was fixed in GCC 16, which is why I only filed it now.) Kudos, and great work keeping CFI accurate!
