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 libc/14267] fprintf() function is multithread-unsafe


http://sourceware.org/bugzilla/show_bug.cgi?id=14267

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

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

--- Comment #2 from Carlos O'Donell <carlos at redhat dot com> 2013-05-22 14:54:19 UTC ---
Peng,

I agree with David, these changes need to be considered carefully because
fprintf() is a function that everyone uses. Simply adding a lock here is going
to impact performance for everyone.

I suggest you follow Alex's posted patches and the discussion threads here:
http://sourceware.org/ml/libc-alpha/2013-03/msg00581.html
http://sourceware.org/ml/libc-alpha/2013-04/msg00023.html
http://sourceware.org/ml/libc-alpha/2013-05/msg00120.html

The first step is going to be to document the exact contract we want to have
with our users, including possibly declaring that register_printf_specifier()
is MT-unsafe, but that fprintf() *IS* MT-safe with exceptions (don't call
register_printf_specifier).

I encourage you to review Alex's work and provide feedback and help submit bugs
where appropriate.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- 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]