public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Gabriel Dos Reis <Gabriel.Dos-Reis@cmla.ens-cachan.fr>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: c++/2644: g++ produces wrong code
Date: Wed, 25 Apr 2001 21:16:00 -0000 [thread overview]
Message-ID: <20010426041600.4146.qmail@sourceware.cygnus.com> (raw)
The following reply was made to PR c++/2644; it has been noted by GNATS.
From: Gabriel Dos Reis <Gabriel.Dos-Reis@cmla.ens-cachan.fr>
To: "Uwe F. Mayer" <mayer@tux.org>
Cc: <gcc-gnats@gcc.gnu.org>
Subject: Re: c++/2644: g++ produces wrong code
Date: 26 Apr 2001 06:13:20 +0200
"Uwe F. Mayer" <mayer@tux.org> writes:
| >Environment:
| System: Linux tosca 2.2.18 #2 Thu Mar 8 13:48:25 PST 2001 i686 unknown
| Architecture: i686
| host: i686-pc-linux-gnu
| build: i686-pc-linux-gnu
| target: i686-pc-linux-gnu
| configured with: ../gcc/configure --prefix=/usr/local/gcc --disable-nls
| >Description:
| The calls
| numeric_limits<wchar_t >::digits
| and
| numeric_limits<wchar_t >::max()
| return zero (0) instead of the limits of the type w_char.
This is indeed a bug. Actually, it is the specialization
numeric_limits<wchar_t> which is missing.
| >Fix:
| I assume that ..../lib/gcc-lib/i686-pc-linux-gnu/3.0/include/limits.h
| needs to be fixed.
Actually -not-. That file it C bits. The right fix should happen in
mknumeric_limits and gen-num-limits.cc
-- Gaby
next reply other threads:[~2001-04-25 21:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-25 21:16 Gabriel Dos Reis [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-25 13:16 Uwe F. Mayer
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=20010426041600.4146.qmail@sourceware.cygnus.com \
--to=gabriel.dos-reis@cmla.ens-cachan.fr \
--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: 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).