public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Andreas Jaeger <aj@suse.de> To: aj@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: libstdc++/8610: std::streamoff type is 32-bit in GCC 3.2 whereas it was 64-bit in GCC 2.96 Date: Sun, 09 Feb 2003 10:26:00 -0000 [thread overview] Message-ID: <20030209102601.302.qmail@sources.redhat.com> (raw) The following reply was made to PR libstdc++/8610; it has been noted by GNATS. From: Andreas Jaeger <aj@suse.de> To: Paolo Carlini <pcarlini@unitus.it> Cc: paolo@gcc.gnu.org, davido@csse.uwa.edu.au, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: libstdc++/8610: std::streamoff type is 32-bit in GCC 3.2 whereas it was 64-bit in GCC 2.96 Date: Sun, 09 Feb 2003 11:21:38 +0100 Paolo Carlini <pcarlini@unitus.it> writes: > Andreas Jaeger wrote: > >>Paolo, I need some help here since I don't know the internals of >>libstc++. >> > Hi Andreas and thanks for your _very_ quick reply! > My impression, in general, is that enabling LFS for libstdc++ is a > new project! I would appreciate having some general guidelines from > you and trying to work on it in the next few months... > So: > >>/opt/gcc/3.4-devel/include/c++/3.4/i686-pc-linux-gnu/bits/c++io.h >>(where does this file come from?) indeed defines: >> namespace std { >>// for fpos.h >> typedef long streamoff; >> typedef ptrdiff_t streamsize; // Signed integral type >> > It comes from libstdc++-v3/config/io/c_io_stdio.h. It's wrong, right? > What should be, instead, off64_t? It really depends on the functions you use - if you use fseek/ftell, it's right. But if you compile with _FILE_OFFSET_BITS=64 and use ftello/fseeko, you need off_t which is in this case a 64-bit variable. Or use fseeko64/ftello64 with off64_t, or fsetpos64/fgetpos64 with fpos64_t. > Is this the correct type, which becomes a real 64 bit type as soon > as _FILE_OFFSET_BITS=64 is defined? off_t becomes 64-bit if you use that define. > Also, why _two_ different defines are needed, both _FILE_OFFSET_BITS=64 > and _LARGEFILE_SOURCE ?? Could you please explain a bit? _FILE_OFFSET_BITS=64 basically renames the types and functions so that instead of fsetpos, fsetpos64 is called. _LARGEFILE_SOURCE gives only the declaration for 64-bit types and functions without the renaming, so that your program can use both fsetpos and fsetpos64. >>And libstdc++/config/io/c_io_libio.h has: >> > Disregard this file: it was only used by the old libio. > >>But the problem is even more subitle. config/io/basic_file_stdio.cc >>uses fseek/ftell which use a long int and therefore - under 32-bit - >>allow only 2 GB. You should use fseeko/ftello or fsetpos/fgetpos. >> > I see... Isn't possible to have a single name for both 32 and 64 bit > which transparently adapts according to the value of the defines?? > Is it fseeko/ftello? Yes - or fsetpos/fgetpos. > I read in the glibc docs that open64 for instance can be avoided and > only open used transaparently... With _FILE_OFFSET_BITS=64 > In your opinion, which amount of transparency can be achieved? > I mean, it will ever be possible to have one single libstdc++, which, > without configure magic, becomes LFS only by setting > _FILE_OFFSET_BITS=64 and _LARGEFILE_SOURCE when it's compiled? Using _FILE_OFFSET_BITS=64 would work if we use off_t and avoid fseek/ftell. But it might give an incompatible lib depending which define is use. I therefore advise to use _LARGEFILE_SOURCE only and call the 64-bit functions directly. > Thanks for your past and future help, ;-) Btw. What shall we do with this PR? Andreas -- Andreas Jaeger SuSE Labs aj@suse.de private aj@arthur.inka.de http://www.suse.de/~aj
next reply other threads:[~2003-02-09 10:26 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-09 10:26 Andreas Jaeger [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-02-09 13:20 paolo 2003-02-09 12:06 Paolo Carlini 2003-02-08 21:56 Paolo Carlini 2003-02-08 21:36 Andreas Jaeger 2003-02-08 20:31 paolo 2002-11-22 10:26 davido
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=20030209102601.302.qmail@sources.redhat.com \ --to=aj@suse.de \ --cc=aj@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.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: linkBe 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).