public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gdr at integrable-solutions dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/13005] Pointer wrongly adjusted for derived class containing virtual function Date: Sat, 10 Jan 2004 02:16:00 -0000 [thread overview] Message-ID: <20040110021635.3449.qmail@sources.redhat.com> (raw) In-Reply-To: <20031111075141.13005.stephenma@telus.net> ------- Additional Comments From gdr at integrable-solutions dot net 2004-01-10 02:16 ------- Subject: Re: Pointer wrongly adjusted for derived class containing virtual function "stephenma at telus dot net" <gcc-bugzilla@gcc.gnu.org> writes: | > As a matter of existing practrice, we don't say "see xxxx". | | Omitting the "see xxx" would do more harm than good. The g++ | maintainers would be flooded with questions about the warning. | | If you intend to be rigid about this, please tell me now. I would | prefer to withdraw the patch rather than be blamed by people who do | not understand what the warning means. I don't mean to be ridig about it. I'm pointing out a fact and would like that to be taken into account, when you will be submitting a revised version. -- Gaby -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13005
next prev parent reply other threads:[~2004-01-10 2:16 UTC|newest] Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-11-11 7:51 [Bug c++/13005] New: " stephenma at telus dot net 2003-11-11 16:01 ` [Bug c++/13005] " bangerth at dealii dot org 2003-11-11 17:54 ` bangerth at dealii dot org 2003-11-11 17:57 ` bangerth at dealii dot org 2003-11-15 9:10 ` [Bug c++/13005] [aliasing] " pinskia at gcc dot gnu dot org 2003-11-15 9:10 ` pinskia at gcc dot gnu dot org 2003-11-16 12:04 ` geoffk at gcc dot gnu dot org 2003-12-04 18:38 ` [Bug c++/13005] [3.3/3.4 Regresssion] " pinskia at gcc dot gnu dot org 2003-12-24 15:14 ` jazzdaq at yahoo dot com 2003-12-24 21:55 ` gdr at gcc dot gnu dot org 2003-12-29 20:50 ` nathan at gcc dot gnu dot org 2003-12-31 9:48 ` stephenma at telus dot net 2003-12-31 12:15 ` nathan at gcc dot gnu dot org 2003-12-31 17:57 ` pinskia at gcc dot gnu dot org 2004-01-01 1:02 ` stephenma at telus dot net 2004-01-01 1:09 ` pinskia at gcc dot gnu dot org 2004-01-08 2:02 ` stephenma at telus dot net 2004-01-08 2:24 ` [Bug c++/13005] " pinskia at gcc dot gnu dot org 2004-01-08 8:10 ` falk dot hueffner at student dot uni-tuebingen dot de 2004-01-08 18:13 ` gdr at integrable-solutions dot net 2004-01-09 1:33 ` stephenma at telus dot net 2004-01-09 1:46 ` stephenma at telus dot net 2004-01-09 4:17 ` gdr at integrable-solutions dot net 2004-01-09 4:24 ` gdr at integrable-solutions dot net 2004-01-09 8:40 ` stephenma at telus dot net 2004-01-09 8:46 ` stephenma at telus dot net 2004-01-09 15:16 ` bangerth at dealii dot org 2004-01-10 2:13 ` gdr at integrable-solutions dot net 2004-01-10 2:16 ` gdr at integrable-solutions dot net [this message] 2004-01-10 5:45 ` stephenma at telus dot net 2004-01-10 5:48 ` stephenma at telus dot net 2004-01-10 5:53 ` stephenma at telus dot net 2004-01-10 16:02 ` gdr at integrable-solutions dot net 2004-07-27 3:13 ` [Bug c++/13005] Pointer " pinskia at gcc dot gnu dot org 2005-09-23 22:35 ` pinskia 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=20040110021635.3449.qmail@sources.redhat.com \ --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).