public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dimitrisdad at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/53225] static operator new in multiple inheritance carries incorrect type information for the class Date: Fri, 04 May 2012 19:25:00 -0000 [thread overview] Message-ID: <bug-53225-4-JCU8YrxNbC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53225-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53225 --- Comment #9 from Thomas W. Lynch <dimitrisdad at gmail dot com> 2012-05-04 19:25:08 UTC --- I went to take 'this_type' out of the source. You were correct to focus on that. As malloc() returns a void * there must be a cast to access the fields in the instance. We routinely use 'this_type' in our shop, which is defined to be the same as the class name. However, if you put the class name in, e.g. (A *) malloc(..) then you would definitely get the offset for an A, even after the method is inherited into a B. The question comes down to, then, if when inheriting a method into a child, if the typedefs in the child apply or the typedefs in the parent apply. It should be the typedefs of the child, as offsets (type) is adjusted in inheritance. It would eliminate a lot of otherwise valid looking code otherwise. This looks to be a general issue with multiple inheritance having nothing to do with operator new. Let me check that.. Though lets also keep in mind, the compiler makes no noise at all in this situation.
next prev parent reply other threads:[~2012-05-04 19:25 UTC|newest] Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-05-04 3:30 [Bug c++/53225] New: " dimitrisdad at gmail dot com 2012-05-04 3:35 ` [Bug c++/53225] " dimitrisdad at gmail dot com 2012-05-04 3:41 ` pinskia at gcc dot gnu.org 2012-05-04 5:21 ` dimitrisdad at gmail dot com 2012-05-04 8:55 ` redi at gcc dot gnu.org 2012-05-04 9:44 ` redi at gcc dot gnu.org 2012-05-04 18:12 ` dimitrisdad at gmail dot com 2012-05-04 18:32 ` redi at gcc dot gnu.org 2012-05-04 18:57 ` dimitrisdad at gmail dot com 2012-05-04 19:25 ` dimitrisdad at gmail dot com [this message] 2012-05-04 19:45 ` redi at gcc dot gnu.org 2012-05-04 19:59 ` dimitrisdad at gmail dot com 2012-05-04 20:02 ` dimitrisdad at gmail dot com 2012-05-04 20:10 ` daniel.kruegler at googlemail dot com 2012-05-04 20:18 ` dimitrisdad at gmail dot com 2012-05-04 20:35 ` redi at gcc dot gnu.org 2012-05-04 20:56 ` dimitrisdad at gmail dot com 2012-05-04 20:59 ` redi at gcc dot gnu.org 2012-05-04 21:07 ` redi at gcc dot gnu.org 2012-05-04 21:16 ` dimitrisdad at gmail dot com 2012-05-04 21:27 ` dimitrisdad at gmail dot com 2012-05-04 21:30 ` redi at gcc dot gnu.org 2012-05-04 21:41 ` dimitrisdad at gmail dot com 2012-05-04 21:52 ` redi at gcc dot gnu.org 2012-05-04 21:56 ` redi at gcc dot gnu.org 2012-05-04 22:01 ` dimitrisdad at gmail dot com 2012-05-04 22:05 ` daniel.kruegler at googlemail dot com 2012-05-04 22:07 ` pinskia at gcc dot gnu.org 2012-05-04 22:09 ` redi at gcc dot gnu.org 2012-05-04 22:31 ` dimitrisdad at gmail dot com 2012-05-04 22:55 ` dimitrisdad at gmail dot com 2012-05-04 23:21 ` redi at gcc dot gnu.org 2012-05-04 23:37 ` dimitrisdad at gmail dot com 2012-05-04 23:37 ` dimitrisdad at gmail dot com 2012-05-05 0:04 ` pinskia at gcc dot gnu.org 2012-05-05 0:15 ` redi at gcc dot gnu.org 2012-05-05 0:49 ` dimitrisdad at gmail 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-53225-4-JCU8YrxNbC@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).