public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <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: Sat, 05 May 2012 00:15:00 -0000 [thread overview]
Message-ID: <bug-53225-4-JY8j6iuG7w@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 #32 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-05-05 00:14:38 UTC ---
(In reply to comment #30)
> Sorry to be thick headed Jon. Perhaps you could boil it down to the essentials
> here, are you saying that assignment is illegal in operator new so it is proper
> that there be no error and one gets the wrong result? Is that your point?
> Answer me this, and I will drop the report.
No, I'm saying you are not getting the wrong result. What you think is correct
is not correct.
I'm saying the behaviour you see is not a compiler bug, it's how C++ works.
This bug report is *not* the right place to discuss it, take it to the gcc-help
mailing list or *anywhere* else. "I don't understand C++" is not a valid bug.
So I'm moving this to gcc-help and I'm closing the report again, if the
description Please stop re-opening this report. I will discuss it elsewhere but
not here.
See http://gcc.gnu.org/ml/gcc-help/2012-05/msg00029.html for anyone who isn't
sick of this yet.
next prev parent reply other threads:[~2012-05-05 0:15 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
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 [this message]
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-JY8j6iuG7w@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: link
Be 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).