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++/22238] [4.0/4.1 regression] '#'obj_type_ref' not supported by dump_expr
Date: Thu, 30 Jun 2005 03:19:00 -0000	[thread overview]
Message-ID: <20050630031939.17484.qmail@sourceware.org> (raw)
In-Reply-To: <20050629232130.22238.reichelt@gcc.gnu.org>


------- Additional Comments From gdr at integrable-solutions dot net  2005-06-30 03:19 -------
Subject: Re:  New: [4.0/4.1 regression] '#'obj_type_ref' not supported by dump_expr

"reichelt at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> writes:

| Since GCC 4.0.0 the compiler issues a hosed error message for the
| following invalid code snippet:
| 
| ======================================
| struct A
| {
|   virtual void foo();
|   void bar() { if (foo()) ; }
| };
| ======================================
| 
| The error message reads:
|   bug.cc: In member function 'void A::bar()':
|   bug.cc:4: error: could not convert '#'obj_type_ref' not supported by
| dump_expr#<expression error>(this)' to 'bool'

I think I crossed this silly behaviour from the error.c several types,
but it was always in a bigger context.  Thanks for reducing it to this
small.  I'll fix it. 

| With GCC 3.4.4 I get
|   bug.cc: In member function `void A::bar()':
|   bug.cc:4: error: could not convert `(**((A*)this)->A::_vptr.A)(((A*)this))' to
| `bool'
| which is better, but not optimal.

Agreed.

-- Gaby


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22238


  parent reply	other threads:[~2005-06-30  3:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-29 23:21 [Bug c++/22238] New: " reichelt at gcc dot gnu dot org
2005-06-30  2:00 ` [Bug c++/22238] " pinskia at gcc dot gnu dot org
2005-06-30  2:26 ` pinskia at gcc dot gnu dot org
2005-06-30  3:19 ` gdr at integrable-solutions dot net [this message]
2005-06-30  3:20 ` gdr at integrable-solutions dot net
2005-06-30  3:25 ` pinskia at gcc dot gnu dot org
2005-07-03 14:11 ` gdr at gcc dot gnu dot org
2005-09-27 16:13 ` mmitchel at gcc dot gnu dot org
     [not found] <bug-22238-1771@http.gcc.gnu.org/bugzilla/>
2005-10-13 19:55 ` pinskia at gcc dot gnu dot org
2005-10-31  3:55 ` mmitchel at gcc dot gnu dot org
2005-11-16 19:05 ` gdr at integrable-solutions dot net

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=20050630031939.17484.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: 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).