public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rjarrett at mathworks dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/56086] New: when compiling C code with -std=gnu99 macro __STDC_UTF_16__ is defined Date: Wed, 23 Jan 2013 19:26:00 -0000 [thread overview] Message-ID: <bug-56086-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56086 Bug #: 56086 Summary: when compiling C code with -std=gnu99 macro __STDC_UTF_16__ is defined Classification: Unclassified Product: gcc Version: 4.7.2 Status: UNCONFIRMED Severity: minor Priority: P3 Component: c AssignedTo: unassigned@gcc.gnu.org ReportedBy: rjarrett@mathworks.com Created attachment 29255 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29255 sample program The macro __STDC_UTF_16__ is unexpectedly defined when compiling C code using gcc 4.7.2 (also present in gcc 4.7.1) This is a regression from gcc 4.5.3. (also gcc 4.4.6) compilation line: gcc -c -std=gnu99 gcc47_stdc_utf_16.c expected result: no output actual result: gcc47_stdc_utf_16.c:3:2: warning: #warning __STDC_UTF_16__ defined [-Wcpp] use case was in a header file used for both C and C++ compilation that contained #if defined(__STDC_UTF_16__) ... #endif workaround: use :#if (__cplusplus && defined(__STDC_UTF_16__)) in place of #if defined(__STDC_UTF_16__)
next reply other threads:[~2013-01-23 19:26 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-01-23 19:26 rjarrett at mathworks dot com [this message] 2013-01-23 20:48 ` [Bug c/56086] " joseph at codesourcery dot com 2013-01-27 16:12 ` rjarrett at mathworks dot com 2013-01-27 16:14 ` rjarrett at mathworks dot com 2013-01-28 3:43 ` joseph at codesourcery dot com 2013-01-28 8:29 ` jakub at gcc dot gnu.org 2013-01-29 17:43 ` jason at gcc dot gnu.org
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=bug-56086-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).