This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug dynamic-link/19917] Bad threading regression starting with f3dcae82d54e5097e18e1d6ef4ff55c2ea4e621e


https://sourceware.org/bugzilla/show_bug.cgi?id=19917

Carlos O'Donell <carlos at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |carlos at redhat dot com

--- Comment #8 from Carlos O'Donell <carlos at redhat dot com> ---
I will note that commit f3dcae82d54e5097e18e1d6ef4ff55c2ea4e621e should only
have impacted the first call to a given function e.g. slowdown caused by
save/restore of more registers during the lazy symbol resolution path.
Subsequent calls should have been just as fast. Something else is happening
here, but given the resolution by the user I'm happy to ignore this as a
problem with libx264.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]