public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug nptl/28458] pthread_setspecific rejects pseudo pointers
Date: Thu, 04 Nov 2021 07:00:23 +0000 [thread overview]
Message-ID: <bug-28458-131-HjwZJBaNlv@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28458-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28458
Florian Weimer <fweimer at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2021-11-04
Ever confirmed|0 |1
Status|RESOLVED |REOPENED
Resolution|MOVED |---
--- Comment #5 from Florian Weimer <fweimer at redhat dot com> ---
It's not just pseudo-pointers, we get a warning for this as well:
#include <pthread.h>
extern int x[1];
void
f (pthread_key_t key)
{
pthread_setspecific (key, &x[1]);
}
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-11-04 7:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-16 7:53 [Bug nptl/28458] New: " jan.kiszka at siemens dot com
2021-10-16 20:51 ` [Bug nptl/28458] " vt at altlinux dot org
2021-10-18 11:11 ` glebfm at altlinux dot org
2021-10-18 13:35 ` fweimer at redhat dot com
2021-10-18 13:36 ` fweimer at redhat dot com
2021-10-18 13:46 ` jan.kiszka at siemens dot com
2021-10-18 13:50 ` fweimer at redhat dot com
2021-11-04 7:00 ` fweimer at redhat dot com [this message]
2021-11-04 7:00 ` fweimer at redhat dot com
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-28458-131-HjwZJBaNlv@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: link
Be 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).