public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl dot tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/39494] Bad assembly when derived class has same name as virtual method Date: Wed, 18 Mar 2009 16:16:00 -0000 [thread overview] Message-ID: <20090318161629.20031.qmail@sourceware.org> (raw) In-Reply-To: <bug-39494-17469@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from hjl dot tools at gmail dot com 2009-03-18 16:16 ------- Icc ia32 generates: _ZTV7Derived: .type _ZTV7Derived,@object .size _ZTV7Derived,12 .long 0 .long _ZTI7Derived .long __cxa_pure_virtual Gcc generates: .size _ZTV7Derived, 24 _ZTV7Derived: .long 0 .long _ZTI7Derived .long __cxa_pure_virtual .long _ZN7DerivedC1Ev *INTERNAL* .long _ZN7DerivedC2Ev .long _ZN7DerivedC1Ev -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39494
next prev parent reply other threads:[~2009-03-18 16:16 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-03-18 14:31 [Bug c++/39494] New: " james dot ashley at gmail dot com 2009-03-18 14:33 ` [Bug c++/39494] " james dot ashley at gmail dot com 2009-03-18 14:57 ` rguenth at gcc dot gnu dot org 2009-03-18 16:16 ` hjl dot tools at gmail dot com [this message] [not found] <bug-39494-4@http.gcc.gnu.org/bugzilla/> 2014-06-24 11:53 ` paolo.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=20090318161629.20031.qmail@sourceware.org \ --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).