public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sbergman at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/58138] New: #include <random> gives warning: macro "__code_model_small__" is not used Date: Mon, 12 Aug 2013 16:24:00 -0000 [thread overview] Message-ID: <bug-58138-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58138 Bug ID: 58138 Summary: #include <random> gives warning: macro "__code_model_small__" is not used Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: sbergman at redhat dot com At least with a trunk revision 201654 (aka LATEST-4.9) build (on Fedora 18 x86_64): > $ cat test1.cc > #include <random> > namespace {} > $ ~/gcc/LATEST-4.9/inst/bin/g++ -std=gnu++11 -Wunused-macros -c test1.cc > test1.cc:2:12: warning: macro "__code_model_small__" is not used [-Wunused-macros] > namespace {} > ^ I was able to strip that down to the following excerpt of ~/gcc/LATEST-4.9/inst/lib/gcc/x86_64-unknown-linux-gnu/4.9.0/include/ia32intrin.h: > $ cat test2.cc > #include "test2.h" > namespace {} > $ cat test2.h > #pragma GCC system_header > #pragma GCC push_options > #pragma GCC target("sse4.2") > #pragma GCC pop_options > $ ~/gcc/LATEST-4.9/inst/bin/g++ -Wunused-macros -c test2.cc test2.cc:2:12: warning: macro "__code_model_small__" is not used [-Wunused-macros] > namespace {} > ^ With a build of tags/gcc_4_8_1_release, compiling test1.cc does not give a warning while test2.cc does. And with a random old build of branches/gcc-4_6-branch, compiling neither test1.cc nor test2.cc gives a warning (replacing -std=gnu++11 with -std=gnu++0x when compiling test1.cc).
next reply other threads:[~2013-08-12 16:24 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-08-12 16:24 sbergman at redhat dot com [this message] 2015-04-09 14:52 ` [Bug libstdc++/58138] " redi 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-58138-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).