public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "idonotknow232 at comcast dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/17086] IOStreams Large File Support (> 2 GB) not fully implemented.
Date: Wed, 18 Aug 2004 21:24:00 -0000	[thread overview]
Message-ID: <20040818212410.27177.qmail@sourceware.org> (raw)
In-Reply-To: <20040818192027.17086.idonotknow232@comcast.net>


------- Additional Comments From idonotknow232 at comcast dot net  2004-08-18 21:24 -------
Paolo,

Tried described code in small test program.  This seems to works for files > 
and < 2GB.  I am stumped why it works in my small test program and not in my 
app.  I will need to perform more testing.  I will pull my app apart and try to 
isolate problem.  The code is tucked away in a class and I may need to isolate 
the class and test the class by itself.  I will let you know if I can reproduce.

-- Robert

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
  GCC build triplet|3.4.1                       |sparc-sun-solaris2.8
   GCC host triplet|3.4.1                       |sparc-sun-solaris2.8
 GCC target triplet|3.4.1                       |sparc-sun-solaris2.8


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17086


  parent reply	other threads:[~2004-08-18 21:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040818192027.17086.idonotknow232@comcast.net>
2004-08-18 20:18 ` pcarlini at suse dot de
2004-08-18 20:18 ` pcarlini at suse dot de
2004-08-18 20:42 ` pcarlini at suse dot de
2004-08-18 21:24 ` idonotknow232 at comcast dot net [this message]
2004-09-06 20:04 ` pcarlini at suse dot de
2004-08-18 19:20 [Bug libstdc++/17086] New: " scrimr at louisville dot stortek dot com
2004-08-18 19:28 ` [Bug libstdc++/17086] " pinskia at gcc dot gnu dot org

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=20040818212410.27177.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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: 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).