public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "loose at astron dot nl" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/21210] New: STL containers do not accept GNU builtin __complex__ type anymore Date: Mon, 25 Apr 2005 09:58:00 -0000 [thread overview] Message-ID: <20050425095627.21210.loose@astron.nl> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 2640 bytes --] The GCC 4.0.0 release does not support the use of the GNU builtin __complex__ anymore in, e.g., std::vector. The code below used to compile on GNU (compatible) compilers prior to GCC 4.0 <code> #include <vector> typedef float __complex__ fcomplex; std::vector<fcomplex> vfc(10); </code> GCC 4.0.0 produces the following diagnostic: $ /data/loose/gcc-4.0.0/bin/g++ -v -save-temps -c -Wall -W tVec.cc Using built-in specs. Target: i686-pc-linux-gnu Configured with: ../../src/gcc-4.0.0/configure --prefix=/data/loose/gcc-4.0.0 --enable-threads --enable-__cxa_atexit Thread model: posix gcc version 4.0.0 /data/loose/gcc-4.0.0/libexec/gcc/i686-pc-linux-gnu/4.0.0/cc1plus -E -quiet -v -D_GNU_SOURCE tVec.cc -mtune=pentiumpro -Wall -W -fpch-preprocess -o tVec.ii ignoring nonexistent directory "/data/loose/gcc-4.0.0/lib/gcc/i686-pc-linux-gnu/4.0.0/../../../../i686-pc-linux-gnu/include" #include "..." search starts here: #include <...> search starts here: /data/loose/gcc-4.0.0/lib/gcc/i686-pc-linux-gnu/4.0.0/../../../../include/c++/4.0.0 /data/loose/gcc-4.0.0/lib/gcc/i686-pc-linux-gnu/4.0.0/../../../../include/c++/4.0.0/i686-pc-linux-gnu /data/loose/gcc-4.0.0/lib/gcc/i686-pc-linux-gnu/4.0.0/../../../../include/c++/4.0.0/backward /usr/local/include /data/loose/gcc-4.0.0/include /data/loose/gcc-4.0.0/lib/gcc/i686-pc-linux-gnu/4.0.0/include /usr/include End of search list. /data/loose/gcc-4.0.0/libexec/gcc/i686-pc-linux-gnu/4.0.0/cc1plus -fpreprocessed tVec.ii -quiet -dumpbase tVec.cc -mtune=pentiumpro -auxbase tVec -Wall -W -version -o tVec.s GNU C++ version 4.0.0 (i686-pc-linux-gnu) compiled by GNU C version 4.0.0. GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072 /data/loose/gcc-4.0.0/lib/gcc/i686-pc-linux-gnu/4.0.0/../../../../include/c++/4.0.0/bits/stl_vector.h: In constructor std::vector<_Tp, _Alloc>::vector(size_t) [with _Tp = float __complex__, _Alloc = std::allocator<float __complex__>]: tVec.cc:3: instantiated from here /data/loose/gcc-4.0.0/lib/gcc/i686-pc-linux-gnu/4.0.0/../../../../include/c++/4.0.0/bits/stl_vector.h:219: error: invalid cast from type int to type float __complex__ -- Summary: STL containers do not accept GNU builtin __complex__ type anymore Product: gcc Version: 4.0.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: loose at astron dot nl CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21210
next reply other threads:[~2005-04-25 9:58 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-04-25 9:58 loose at astron dot nl [this message] 2005-04-25 11:59 ` [Bug c++/21210] Trouble with __complex__ types default construction pcarlini at suse dot de 2005-04-25 13:24 ` [Bug c++/21210] [4.0/4.1 Regression] " pinskia at gcc dot gnu dot org 2005-05-29 6:16 ` mmitchel at gcc dot gnu dot org 2005-05-29 23:02 ` mmitchel at gcc dot gnu dot org 2005-06-01 0:33 ` pinskia at gcc dot gnu dot org 2005-06-02 5:04 ` mmitchel at gcc dot gnu dot org 2005-07-06 17:03 ` mmitchel at gcc dot gnu dot org 2005-09-05 17:03 ` mmitchel at gcc dot gnu dot 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=20050425095627.21210.loose@astron.nl \ --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).