From: Roland McGrath <roland@redhat.com>
To: GNU libc hackers <libc-hacker@sources.redhat.com>
Subject: ia64 t_scalar_t definition
Date: Fri, 18 Oct 2002 20:55:00 -0000 [thread overview]
Message-ID: <200210190343.g9J3hNn02855@magilla.sf.frob.com> (raw)
t_scalar_t and t_uscalar_t are defined as 32 bits on ia64, while on other
platforms they seem to be the word size. Is that really right?
These types seem only to be used by some STREAMS structures that nothing in
libc itself uses, so I don't know what if anything has ever actually used
these types.
reply other threads:[~2002-10-19 3:43 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=200210190343.g9J3hNn02855@magilla.sf.frob.com \
--to=roland@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).