public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug nptl/16063] New: Provide a pthread_once variant in libc directly
@ 2013-10-18 15:18 fweimer at redhat dot com
  2014-06-13 12:38 ` [Bug nptl/16063] " fweimer at redhat dot com
  2021-05-31 18:11 ` adhemerval.zanella at linaro dot org
  0 siblings, 2 replies; 3+ messages in thread
From: fweimer at redhat dot com @ 2013-10-18 15:18 UTC (permalink / raw)
  To: glibc-bugs

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

            Bug ID: 16063
           Summary: Provide a pthread_once variant in libc directly
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: nptl
          Assignee: unassigned at sourceware dot org
          Reporter: fweimer at redhat dot com
                CC: drepper.fsp at gmail dot com

pthread_once is useful as a uniform initialization interface in libraries, even
if threads are not used.  If it were available unconditionally, libraries could
use it directly, without having to supply their own implementation for the
no-threads case.

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


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug nptl/16063] Provide a pthread_once variant in libc directly
  2013-10-18 15:18 [Bug nptl/16063] New: Provide a pthread_once variant in libc directly fweimer at redhat dot com
@ 2014-06-13 12:38 ` fweimer at redhat dot com
  2021-05-31 18:11 ` adhemerval.zanella at linaro dot org
  1 sibling, 0 replies; 3+ messages in thread
From: fweimer at redhat dot com @ 2014-06-13 12:38 UTC (permalink / raw)
  To: glibc-bugs

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

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|                            |security-

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


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug nptl/16063] Provide a pthread_once variant in libc directly
  2013-10-18 15:18 [Bug nptl/16063] New: Provide a pthread_once variant in libc directly fweimer at redhat dot com
  2014-06-13 12:38 ` [Bug nptl/16063] " fweimer at redhat dot com
@ 2021-05-31 18:11 ` adhemerval.zanella at linaro dot org
  1 sibling, 0 replies; 3+ messages in thread
From: adhemerval.zanella at linaro dot org @ 2021-05-31 18:11 UTC (permalink / raw)
  To: glibc-bugs

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

Adhemerval Zanella <adhemerval.zanella at linaro dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
   Target Milestone|---                         |2.34
             Status|NEW                         |RESOLVED
                 CC|                            |adhemerval.zanella at linaro dot o
                   |                            |rg

--- Comment #1 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> ---
Fixed on 2.34 (3fec7f18bfcb7044e813a12e19c3c98eb8387e26), now both call_once
and pthread_once are both provided by libc.so.

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2021-05-31 18:11 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-10-18 15:18 [Bug nptl/16063] New: Provide a pthread_once variant in libc directly fweimer at redhat dot com
2014-06-13 12:38 ` [Bug nptl/16063] " fweimer at redhat dot com
2021-05-31 18:11 ` adhemerval.zanella at linaro dot org

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).