From: Roland McGrath <roland@redhat.com>
To: Ulrich Drepper <drepper@redhat.com>
Cc: GNU libc hackers <libc-hacker@sources.redhat.com>
Subject: bits/atomic.h atomic*_t types
Date: Sun, 30 Mar 2003 23:40:00 -0000 [thread overview]
Message-ID: <200303302333.h2UNX4w00611@magilla.sf.frob.com> (raw)
AFAIK the atomic*_t types have not been used for anything yet. There are
no comments on the definitions (bad), so I am guessing what they are for.
Are they intended to be like int_fastNN_t, i.e. a type that is at least
that large and can be accessed atomically? (The existing uses of atomic.h
assume that int and word/pointer size are usable atomically rather than
using these types, which is probably safe.)
All the bits/atomic.h files have copied the verbatim definitions from the
original i386 file. All 4 sizes can be accessed with atomic instructions
on i386. But I believe that on almost all other machines, only one or two
sizes (32 and/or 64 bits) really work. So the definitions should be
changed for most machines, no?
Thanks,
Roland
reply other threads:[~2003-03-30 23:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200303302333.h2UNX4w00611@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=drepper@redhat.com \
--cc=libc-hacker@sources.redhat.com \
/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).