public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "john dot salmon at deshaw dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/40856] New: numeric_limits not specialized for __int128_t or __uint128_t Date: Sat, 25 Jul 2009 15:02:00 -0000 [thread overview] Message-ID: <bug-40856-14239@http.gcc.gnu.org/bugzilla/> (raw) salmonj@drdblogin6.en.desres$ cat numeric128.cpp #include <limits> #include <iostream> int main(int argc, char **argv){ std::cout << "__int128_t is_specialized: " << std::numeric_limits<__int128_t>::is_specialized << "\n"; std::cout << "__uint128_t is_specialized: " << std::numeric_limits<__uint128_t>::is_specialized << "\n"; std::cout << "int is_specialized: " << std::numeric_limits<int>::is_specialized << "\n"; return 0; } salmonj@drdblogin6.en.desres$ desres-cleanenv -m gcc/4.4.1-13/bin g++ --std=gnu++0x numeric128.cpp salmonj@drdblogin6.en.desres$ a.out __int128_t is_specialized: 0 __uint128_t is_specialized: 0 int is_specialized: 1 salmonj@drdblogin6.en.desres$ -- Summary: numeric_limits not specialized for __int128_t or __uint128_t Product: gcc Version: 4.4.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: john dot salmon at deshaw dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40856
next reply other threads:[~2009-07-25 15:02 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-07-25 15:02 john dot salmon at deshaw dot com [this message] 2009-07-26 9:26 ` [Bug libstdc++/40856] " paolo dot carlini at oracle dot com 2009-12-17 12:09 ` paolo dot carlini at oracle dot com 2009-12-17 12:10 ` paolo dot carlini at oracle dot com 2010-02-18 14:10 ` paolo dot carlini at oracle dot com 2010-02-18 14:11 ` paolo dot carlini at oracle dot com 2010-05-25 20:57 ` paolo dot carlini at oracle dot com 2010-05-25 21:04 ` paolo dot carlini at oracle dot com
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-40856-14239@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).