public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bkoz@gcc.gnu.org
To: gdr@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: libstdc++/2644
Date: Wed, 02 May 2001 12:16:00 -0000	[thread overview]
Message-ID: <20010502191601.25955.qmail@sourceware.cygnus.com> (raw)

The following reply was made to PR libstdc++/2644; it has been noted by GNATS.

From: bkoz@gcc.gnu.org
To: gcc-gnats@gcc.gnu.org, gdr@gcc.gnu.org, mayer@tux.org, nobody@gcc.gnu.org
Cc:  
Subject: Re: libstdc++/2644
Date: 2 May 2001 19:11:37 -0000

 Synopsis: g++ produces wrong code
 
 Responsible-Changed-From-To: unassigned->gdr
 Responsible-Changed-By: bkoz
 Responsible-Changed-When: Wed May  2 12:11:36 2001
 Responsible-Changed-Why:
     Gaby I'm assigning it to you....
 State-Changed-From-To: open->analyzed
 State-Changed-By: bkoz
 State-Changed-When: Wed May  2 12:11:36 2001
 State-Changed-Why:
     Hey folks, I cannot reproduce this with current CVS gcc. I'm not quite sure what is up, but perhaps this bug was filed before wchar_t support was on by default. Can everybody try with current CVS and see what's up?
     here's what I get:
     
     %COMP.sh "-static" 2644.cc
     <bkoz@fillmore> /mnt/hd/bliss/src.gcc/libstdc++-v3/testsuite                    %a.out 
     31	wchar_t digits
     2147483647	wchar_t max
     
     Looks right to me.
     
     -benjamin
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=2644&database=gcc


             reply	other threads:[~2001-05-02 12:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-02 12:16 bkoz [this message]
2001-05-08 23:46 libstdc++/2644 bkoz
2001-06-05 13:46 libstdc++/2644 pme

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=20010502191601.25955.qmail@sourceware.cygnus.com \
    --to=bkoz@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=gdr@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).