https://bugs.kde.org/show_bug.cgi?id=415293
--- Comment #1 from pcpa <paulo.cesar.pereira.de.andr...@gmail.com> ---
As an extra note, there are several different _dl_runtime_resolve{EXT}
variants. I believe only one is used in an application, but there are
multiple names.
A possible fix is to use the logic in callgrind/fn.c so that when a
function matching the initial _dl_runtime_resolve is called, use the
existing code.
A quick grep shows "EXT" as _xsave, _xsavec, _fxsave, _old, _new,
_0, _1, _avx, _avx512, _sse, _sse_vex, _opt... On different versions
of recent (2 or less years) glibc trees.
--
You are receiving this mail because:
You are watching all bug changes.
