From: Roland McGrath <roland@hack.frob.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: <libc-alpha@sourceware.org>, <libc-ports@sourceware.org>
Subject: Re: [PATCH roland/off64_t] clean up wordsize-64 off_t functions
Date: Thu, 02 Aug 2012 20:54:00 -0000 [thread overview]
Message-ID: <20120802205404.E99322C0AC@topped-with-meat.com> (raw)
In-Reply-To: Joseph S. Myers's message of Thursday, 2 August 2012 20:46:34 +0000 <Pine.LNX.4.64.1208022043420.28917@digraph.polyomino.org.uk>
> How is this definition *used* by installed headers?
Oh, it's not at all. Good point.
> If installed headers don't use it (only define it), it could be
> conditioned on _LIBC so it's clear it's not a public interface.
We don't do that for other cases like _DIRENT_HAVE_*, so I don't
see a reason to do it here.
> It appears __LP64__ has been defined (if long and pointers are 64-bit and
> int is 32-bit) since at least GCC 3.4.
Good to know. I'll use that in bits/typesizes.h and that should cover
ia64 and powerpc64 just fine.
Thanks,
Roland
next prev parent reply other threads:[~2012-08-02 20:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 17:21 Roland McGrath
2012-08-02 18:14 ` Chris Metcalf
2012-08-02 20:23 ` Roland McGrath
2012-08-02 20:46 ` Joseph S. Myers
2012-08-02 20:54 ` Roland McGrath [this message]
2012-08-02 21:47 ` Roland McGrath
2012-08-02 21:55 ` [PATCH roland/dirent64] clean up wordsize-64 struct dirent functions Roland McGrath
2012-08-03 20:12 ` Richard Henderson
2012-08-04 8:30 ` David Miller
2012-08-04 9:23 ` Andreas Schwab
2012-08-04 9:26 ` David Miller
2012-08-04 10:37 ` David Miller
2012-08-04 16:14 ` Chris Metcalf
2012-08-03 19:58 ` [PATCH roland/off64_t] clean up wordsize-64 off_t functions Richard Henderson
2012-08-03 20:12 ` Roland McGrath
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=20120802205404.E99322C0AC@topped-with-meat.com \
--to=roland@hack.frob.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=libc-ports@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).