public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/15767] C++ ABI inconsistency for fpos_t on 64-bit archs
Date: Sun, 21 Jul 2013 22:09:00 -0000 [thread overview]
Message-ID: <bug-15767-131-yoZqbvBIQX@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15767-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=15767
--- Comment #2 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
On Sun, 21 Jul 2013, bugdal at aerifal dot cx wrote:
> With that said, I'm not sure why features.h doesn't make _FILE_OFFSET_BITS a
> complete no-op on 64-bit archs. That would make the issue go away entirely.
In general _FILE_OFFSET_BITS can change types even on 64-bit
architectures. In particular, on MIPS n64, struct stat and struct stat64
are different (I don't know whether this was a historical accident, or an
attempt at binary compatibility with IRIX), with the consequence that n64
does not use sysdeps/unix/sysv/linux/wordsize-64/, and meaning that
_FILE_OFFSET_BITS=64 changes the struct stat layout to match struct stat64
and maps all functions using struct stat to the versions that use struct
stat64 - and for ABI compatibility, it can't stop doing so.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2013-07-21 22:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-21 19:21 [Bug libc/15767] New: " bugdal at aerifal dot cx
2013-07-21 20:34 ` [Bug libc/15767] " schwab@linux-m68k.org
2013-07-21 22:09 ` joseph at codesourcery dot com [this message]
2014-06-13 13:20 ` 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-15767-131-yoZqbvBIQX@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).