public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: wavexx@users.sf.net
To: gcc-gnats@gcc.gnu.org
Subject: c++/3014: gcc3: cin problems with solaris 5.8 and >> extractors
Date: Thu, 31 May 2001 10:16:00 -0000	[thread overview]
Message-ID: <20010531171441.12624.qmail@sourceware.cygnus.com> (raw)

>Number:         3014
>Category:       c++
>Synopsis:       gcc3: cin problems with solaris 5.8 and >> extractors
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu May 31 10:16:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Wave++
>Release:        gcc version 3.0 20010529 (prerelease)
>Organization:
>Environment:
System: Solaris 5.9 x86
Architecture: i686
host: i386-pc-solaris2.8
build: i386-pc-solaris2.8
target: i386-pc-solaris2.8
Configured with: ../gcc/configure --prefix=/opt/gcc-cvs --enable-shared --enable-threads --enable-languages=c++,f77,objc --disable-libgcj
>Description:
When using cin extractors (eg: cin >> astring) I need to
type AT LEAST return 2 times, or insert an EOF (^D) to
effectively stop parsing input.
>How-To-Repeat:
Compile the example:
g++ -o gcc3_trigger gcc3_trigger.cpp
run it:
./gcc3_trigger

On solaris 5.8 I need to type return twice to end the program.
>Fix:
-
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="gcc3_trigger.cpp"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="gcc3_trigger.cpp"

I2luY2x1ZGUgPGlvc3RyZWFtPgojaW5jbHVkZSA8c3RyaW5nPgoKdXNpbmcgc3RkOjpjaW47CnVz
aW5nIHN0ZDo6c3RyaW5nOwoKaW50IG1haW4oKQp7CiAgc3RyaW5nIGJ1ZjsKICBjaW4gPj4gYnVm
Owp9Cg==


                 reply	other threads:[~2001-05-31 10:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20010531171441.12624.qmail@sourceware.cygnus.com \
    --to=wavexx@users.sf.net \
    --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: 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).