public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "danglin at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/23296] Data race in setting function descriptor during lazy binding Date: Mon, 30 Mar 2020 20:45:28 +0000 [thread overview] Message-ID: <bug-23296-131-OUXOCkijnr@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-23296-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=23296 John David Anglin <danglin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #19 from John David Anglin <danglin at gcc dot gnu.org> --- Fixed on trunk by commit 1a044511a3f9020c3f430164e0a6a77426fecd7e. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-03-30 20:45 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-23296-131@http.sourceware.org/bugzilla/> 2020-03-30 20:38 ` cvs-commit at gcc dot gnu.org 2020-03-30 20:45 ` danglin at gcc dot gnu.org [this message] 2020-05-04 19:59 ` cvs-commit at gcc dot gnu.org 2020-05-04 20:01 ` cvs-commit at gcc dot gnu.org 2020-07-08 16:44 ` jsm28 at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-23296-131-OUXOCkijnr@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).