public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: cheinan@primus.com To: gcc-gnats@gcc.gnu.org Subject: c/8901: __WCHAR_MAX__ not defined correctly for -fshort-wchar Date: Wed, 11 Dec 2002 08:36:00 -0000 [thread overview] Message-ID: <20021211163324.18116.qmail@sources.redhat.com> (raw) >Number: 8901 >Category: c >Synopsis: __WCHAR_MAX__ not defined correctly for -fshort-wchar >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Wed Dec 11 08:36:02 PST 2002 >Closed-Date: >Last-Modified: >Originator: Cheinan Marks >Release: gcc version 3.3 20021209 (experimental) >Organization: >Environment: Sun Sparc Solaris 8 >Description: __WCHAR_MAX__ incorrectly defined when -fshort-wchar is used. It set to 32767, but a wchar_t is a short unsigned int (see __WCHAR_TYPE__) and the correct value for an unsigned short is 65535. >How-To-Repeat: liza:~/test> cat empty.cpp int main() { return 0; } liza:~/test Yes Master? ~/gccsnap/gcctarget/bin/g++ -E -dM -fshort-wchar empty.cpp | grep -i wchar #define __WCHAR_MAX__ 32767 #define __WCHAR_TYPE__ short unsigned int #define __WCHAR_UNSIGNED__ 1 >Fix: Workaround: Add -D__WCHAR_MAX__=65535 to command line. >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-12-11 16:36 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-11 8:36 cheinan [this message] 2002-12-11 9:53 neil
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=20021211163324.18116.qmail@sources.redhat.com \ --to=cheinan@primus.com \ --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: 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).