public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "michael dot haubenwallner at salomon dot at" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/29209] New: ICE optimizing passing long double to abstract method while in other abstract's impl Date: Mon, 25 Sep 2006 09:00:00 -0000 [thread overview] Message-ID: <bug-29209-9385@http.gcc.gnu.org/bugzilla/> (raw) Another ICE with long double, now with optimization only: $ cat aa.cc class DataEncoder { public: virtual void put_longdouble(long double) = 0; }; class DataOutputStream { public: virtual void write_longdouble(long double value) = 0; }; class DataOutputStream_impl : virtual public DataOutputStream { public: void write_longdouble(long double value); private: DataEncoder *ec; }; void DataOutputStream_impl::write_longdouble(long double value) { ec->put_longdouble(value); } $ g++ aa.cc -c -O2 aa.cc: In member function 'void DataOutputStream_impl::_ZTv0_n12_N21DataOutputStream_impl16write_longdoubleEe(long double)': aa.cc:21: internal compiler error: in expand_expr_addr_expr_1, at expr.c:6336 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. $ g++ -v Using built-in specs. Target: hppa2.0w-hp-hpux11.11 Configured with: /mnt/toolsjunk/snapshot/src/sasrvb/toolsbox-3.5.1.6pre.20060924/buildroot/gcc/gcc-4.1.1/configure --enable-threads=posix --with-gnu-as --with-as=/tools/snapshot/toolsbox-3.5.1.6pre.20060924/hppa2.0w-hp-hpux11.11/hppa2.0w-hp-hpux11.11/bin/as --without-gnu-ld --with-local-prefix=/tools/snapshot/toolsbox-3.5.1.6pre.20060924/hppa2.0w-hp-hpux11.11 --disable-nls --enable-version-specific-runtime-libs --prefix=/tools/snapshot/toolsbox-3.5.1.6pre.20060924/hppa2.0w-hp-hpux11.11 Thread model: posix gcc version 4.1.1 $ -- Summary: ICE optimizing passing long double to abstract method while in other abstract's impl Product: gcc Version: 4.1.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: michael dot haubenwallner at salomon dot at GCC build triplet: hppa2.0w-hp-hpux11.11 GCC host triplet: hppa2.0w-hp-hpux11.11 GCC target triplet: hppa2.0w-hp-hpux11.11 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29209
next reply other threads:[~2006-09-25 9:00 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-09-25 9:00 michael dot haubenwallner at salomon dot at [this message] 2006-09-25 9:02 ` [Bug c++/29209] " michael dot haubenwallner at salomon dot at 2006-09-26 7:10 ` pinskia at gcc dot gnu dot org 2006-09-26 7:28 ` michael dot haubenwallner at salomon dot at 2006-10-10 23:01 ` danglin at gcc dot gnu dot org 2007-02-03 9:45 ` tbm at cyrius dot com 2007-02-03 14:48 ` dave at hiauly1 dot hia dot nrc dot ca 2007-02-03 15:16 ` dave at hiauly1 dot hia dot nrc dot ca 2007-02-04 1:51 ` dave at hiauly1 dot hia dot nrc dot ca 2007-10-19 21:10 ` tbm at cyrius dot com 2007-10-19 21:13 ` tbm at cyrius dot com 2007-11-07 2:49 ` dave at hiauly1 dot hia dot nrc dot ca 2009-05-05 17:54 ` sje at cup dot hp 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-29209-9385@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).