public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: neil@gcc.gnu.org To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: debug/543 Date: Sun, 01 Apr 2001 00:00:00 -0000 [thread overview] Message-ID: <20010124215600.15684.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR debug/543; it has been noted by GNATS. From: neil@gcc.gnu.org To: gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org, robertlipe@usa.net Cc: Subject: Re: debug/543 Date: 24 Jan 2001 21:47:16 -0000 Synopsis: dwarfout.c ICE during bootstrap simplified State-Changed-From-To: open->feedback State-Changed-By: neil State-Changed-When: Wed Jan 24 13:47:16 2001 State-Changed-Why: Hi Robert, This compiles fine on 586 Linux with CVS GCC. Is this target specific, or is it fixed for you too? http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=543&database=gcc >From pcarlini@unitus.it Sun Apr 01 00:00:00 2001 From: pcarlini@unitus.it To: gcc-gnats@gcc.gnu.org Cc: bkoz@redhat.com Subject: libstdc++/1704: Null output from Josuttis example Date: Sun, 01 Apr 2001 00:00:00 -0000 Message-id: <20010119204609.478.qmail@sourceware.cygnus.com> X-SW-Source: 2001-q1/msg00499.html Content-length: 1700 >Number: 1704 >Category: libstdc++ >Synopsis: Null output from Josuttis example >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Fri Jan 19 12:56:00 PST 2001 >Closed-Date: >Last-Modified: >Originator: Paolo Carlini >Release: gcc version 2.97 20010119 (experimental) or any snapshot in the last weeks >Organization: >Environment: Intel PII, GLIBC2.2.1 >Description: The following code (by N. Josuttis, p.669- of his book) does not produce the expected output (i.e. 31 HEXADECIMAL: 1F): #include <iostream> #include <streambuf> #include <locale> #include <cstdio> class outbuf : public std::streambuf { protected: /* central output function * - print characters in uppercase mode */ virtual int_type overflow (int_type c) { if (c != EOF) { // convert lowercase to uppercase c = std::toupper(c,getloc()); // and write the character to the standard output if (std::putchar(c) == EOF) { return EOF; } } return c; } }; int main() { outbuf ob; // create special output buffer std::ostream out(&ob); // initialize output stream with that output buffer out << "31 hexadecimal: " << std::hex << 31 << std::endl; } >How-To-Repeat: The next example in the book too (outbuf1x.cpp & outbuf1x.hpp) does not produce the expected output P.S.: Thanks to Benjamin Kosnik for having fixed the bug I previously reported! >Fix: Dunno, unfortunately... >Release-Note: >Audit-Trail: >Unformatted: >From mps@sonartech.com.au Sun Apr 01 00:00:00 2001 From: mps@sonartech.com.au To: gcc-gnats@gcc.gnu.org Subject: c++/2136: g++ seems to disregard '::' in '::delete' Date: Sun, 01 Apr 2001 00:00:00 -0000 Message-id: <20010301092659.17769.qmail@sourceware.cygnus.com> X-SW-Source: 2001-q1/msg01836.html Content-length: 932 >Number: 2136 >Category: c++ >Synopsis: g++ seems to disregard '::' in '::delete' >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: rejects-legal >Submitter-Id: net >Arrival-Date: Thu Mar 01 01:36:00 PST 2001 >Closed-Date: >Last-Modified: >Originator: Michael Shepanski >Release: 2.95.2 19991024 >Organization: >Environment: AIX power-pc >Description: #include <sys/types.h> class C { public: int x; // A lot of stuff that main() should NOT use: static char pool [100]; void *operator new (size_t, float) { return pool; } void operator delete (void *, float) {} }; int main () { C *p = ::new C; ::delete p; // confused by the presence of C::delete } >How-To-Repeat: Attempt to compile the code in the "description" section >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2001-04-01 0:00 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-04-01 0:00 neil [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-04-01 0:00 debug/543 Robert Lipe
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=20010124215600.15684.qmail@sourceware.cygnus.com \ --to=neil@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).