public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/35335] [4.2/4.3/4.4 regression] Broken diagnostic: 'expr_stmt' not supported by dump_expr
Date: Fri, 09 Jan 2009 16:53:00 -0000	[thread overview]
Message-ID: <20090109165248.13901.qmail@sourceware.org> (raw)
In-Reply-To: <bug-35335-1771@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from jakub at gcc dot gnu dot org  2009-01-09 16:52 -------
Subject: Bug 35335

Author: jakub
Date: Fri Jan  9 16:51:55 2009
New Revision: 143210

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=143210
Log:
        PR c++/35335
        * error.c (dump_expr): Handle EXPR_STMT like BIND_EXPR.

        * g++.dg/other/error31.C: New testcase.

Added:
    trunk/gcc/testsuite/g++.dg/other/error31.C
Modified:
    trunk/gcc/cp/ChangeLog
    trunk/gcc/cp/error.c
    trunk/gcc/testsuite/ChangeLog


-- 


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


  parent reply	other threads:[~2009-01-09 16:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-23 19:45 [Bug c++/35335] New: [4.1/4.2/4.3/4.4 " reichelt at gcc dot gnu dot org
2008-02-23 19:45 ` [Bug c++/35335] " reichelt at gcc dot gnu dot org
2008-02-24 22:01 ` rguenth at gcc dot gnu dot org
2008-07-04 22:35 ` [Bug c++/35335] [4.2/4.3/4.4 " jsm28 at gcc dot gnu dot org
2008-11-22 18:21 ` steven at gcc dot gnu dot org
2009-01-09 16:53 ` jakub at gcc dot gnu dot org [this message]
2009-01-09 16:54 ` [Bug c++/35335] [4.2/4.3 " jakub at gcc dot gnu dot org
2009-03-31 20:46 ` [Bug c++/35335] [4.3 " jsm28 at gcc dot gnu dot org
2009-08-04 12:40 ` rguenth at gcc dot gnu dot org
2010-04-20 13:40 ` rguenth at gcc dot gnu dot org
2010-04-20 13:40 ` rguenth 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=20090109165248.13901.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).