public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Phil Edwards <pedwards@disaster.jaj.com> To: gdr@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: libstdc++/2644: g++ produces wrong code Date: Wed, 02 May 2001 18:16:00 -0000 [thread overview] Message-ID: <20010503011601.27542.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR libstdc++/2644; it has been noted by GNATS. From: Phil Edwards <pedwards@disaster.jaj.com> To: bkoz@gcc.gnu.org Cc: gdr@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: libstdc++/2644: g++ produces wrong code Date: Wed, 2 May 2001 19:52:58 -0400 On Wed, May 02, 2001 at 07:16:01PM -0000, bkoz@gcc.gnu.org wrote: > 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. Ditto for the trunk, but this morning's 3.0 branch produces zeros. (The submitter specified 3.0 in the "release" field.) I thought the wchar_t change was on the branch now... *looks* ugh, there's a bunch of wchar-related things in the trunk ChangeLog not mentioned in the branch ChangeLog. *sigh* The branch/trunk differences are driving me nuts. If we just did a bulk merge, do you think anyone would notice? :-) -- pedwards at disaster dot jaj dot com | pme at sources dot redhat dot com devphil at several other less interesting addresses in various dot domains The gods do not protect fools. Fools are protected by more capable fools.
next reply other threads:[~2001-05-02 18:16 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-05-02 18:16 Phil Edwards [this message] 2001-05-02 19:46 Benjamin Kosnik 2001-05-02 19:46 Phil Edwards
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=20010503011601.27542.qmail@sourceware.cygnus.com \ --to=pedwards@disaster.jaj.com \ --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: 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).