public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "roman at binarylife dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/43622] New: no C++ typeinfo for __float128 and __int128 Date: Thu, 01 Apr 2010 23:26:00 -0000 [thread overview] Message-ID: <bug-43622-17259@http.gcc.gnu.org/bugzilla/> (raw) $ cat tf-test.cpp #include <typeinfo> typedef float type __attribute__((__mode__(TF))); int main() { return *(typeid(type).name()); } $ g++ tf-test.cpp /tmp/cc8RAh4o.o: In function `main': tf-test.cpp:(.text+0x5): undefined reference to `typeinfo for __float128' collect2: ld returned 1 exit status $ cat ti-test.cpp #include <typeinfo> typedef int type __attribute__((__mode__(TI))); int main() { return *(typeid(type).name()); } $ g++ ti-test.cpp /tmp/ccI1nTTK.o: In function `main': ti-test.cpp:(.text+0x5): undefined reference to `typeinfo for __int128' collect2: ld returned 1 exit status $ g++ --version | head -1 g++ (GCC) 4.5.0 20100401 (experimental) -- Summary: no C++ typeinfo for __float128 and __int128 Product: gcc Version: 4.5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: roman at binarylife dot net GCC build triplet: x86_64-unknown-linux-gnu GCC host triplet: x86_64-unknown-linux-gnu GCC target triplet: x86_64-unknown-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43622
next reply other threads:[~2010-04-01 23:26 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-04-01 23:26 roman at binarylife dot net [this message] 2010-04-09 10:06 ` [Bug libstdc++/43622] " 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-43622-17259@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).