public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: strieder@informatik.uni-kl.de To: gcc-gnats@gcc.gnu.org Subject: libstdc++/6672: <fstream> header produces errors Date: Thu, 16 May 2002 01:56:00 -0000 [thread overview] Message-ID: <20020516085417.18578.qmail@sources.redhat.com> (raw) >Number: 6672 >Category: libstdc++ >Synopsis: <fstream> header produces errors >Confidential: no >Severity: non-critical >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Thu May 16 01:56:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Bernd Strieder >Release: 3.1 >Organization: >Environment: Linux 2.4 i686 >Description: The following file compiles with releases gcc-2.95.3 and snapshot gcc-20020513, but not with gcc-3.1. #include <fstream> int main(void) { std::fstream file ("fstreamtest.txt", std::ios::out); file << "Test"; } The bug occurs in file ..gcc/include/g++-v3/bits/basic_file.h template<typename _CharT> class __basic_file_base: public __c_file_type { __c_file_type is unknown producing a parse error before { >How-To-Repeat: Just compile like g++ -g -O2 fstreamt.cc -o fstreamt In file included from /net/bernd/gcc/include/g++-v3/fstream:48, from fstreamt.cc:1: /net/bernd/gcc/include/g++-v3/bits/basic_file.h:52: parse error before `{' token ... subsequent messages omitted >Fix: not known It seems to be recently introduced, since last snapshot worked. >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-05-16 8:56 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-05-16 1:56 strieder [this message] 2002-05-16 2:20 paolo 2002-05-16 6:41 paolo 2002-05-17 7:54 paolo
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=20020516085417.18578.qmail@sources.redhat.com \ --to=strieder@informatik.uni-kl.de \ --cc=gcc-gnats@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).