public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dgregor at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/36408] [4.3/4.4 regression] ICE with statement expression in template
Date: Fri, 01 Aug 2008 14:07:00 -0000	[thread overview]
Message-ID: <20080801140545.3279.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36408-1771@http.gcc.gnu.org/bugzilla/>



------- Comment #10 from dgregor at gcc dot gnu dot org  2008-08-01 14:05 -------
(In reply to comment #9)
> >  - the error message we give in this case is pretty poor. Here we have an
> >empty initializer, but the error message we get back is "void value not ignored
> >as it ought to be", which really doesn't tell us much of anything about the
> >problem.
> 
> I agree. Though I think addressing that should be best done in another bug
> that we can open straight away when we close this one, if you agree.

Agreed.

> >  - since the statement-expression is obviously empty, can we produce this
> >error message at template definition time, rather than waiting until
> >instantiation time? (If the answer isn't a quick "yes", don't worry about it;
> >I'll eventually be going through the initialization bits to check more of them
> >at template definition time anyway.)
> 
> Yes, that would be handy. Though here again, I think we should be opening
> another bug to track that.

It's probably not worth opening a bug report for this, unless it's some
placeholder bug that says, "we should diagnose as many errors as template
definition time as possible." Such a bug is almost impossible to close :)

Your updated patch looks good, but I can't approve it. I suggesting pinging
Jason to get approval.


-- 


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


  parent reply	other threads:[~2008-08-01 14:07 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-01 10:46 [Bug c++/36408] New: " reichelt at gcc dot gnu dot org
2008-06-01 10:47 ` [Bug c++/36408] " reichelt at gcc dot gnu dot org
2008-06-06 15:05 ` rguenth at gcc dot gnu dot org
2008-06-06 20:30 ` rguenth at gcc dot gnu dot org
2008-06-11  6:32 ` jakub at gcc dot gnu dot org
2008-06-11  6:49 ` jakub at gcc dot gnu dot org
2008-06-12 10:14 ` jakub at gcc dot gnu dot org
2008-08-01  8:56 ` dodji at gcc dot gnu dot org
2008-08-01  8:56 ` dodji at gcc dot gnu dot org
2008-08-01  9:09 ` paolo dot carlini at oracle dot com
2008-08-01  9:34 ` dodji at gcc dot gnu dot org
2008-08-01 11:57 ` dgregor at gcc dot gnu dot org
2008-08-01 13:33 ` dodji at gcc dot gnu dot org
2008-08-01 14:07 ` dgregor at gcc dot gnu dot org [this message]
2008-08-01 17:56 ` dodji at gcc dot gnu dot org
2008-08-27 22:09 ` jsm28 at gcc dot gnu dot org
2009-01-24 10:24 ` rguenth at gcc dot gnu dot org
2009-08-04 12:40 ` [Bug c++/36408] [4.3/4.4/4.5 " rguenth at gcc dot gnu dot org
2009-11-28  9:23 ` dodji at gcc dot gnu dot org
2009-11-28 22:56 ` dodji at gcc dot gnu dot org
2009-11-28 22:58 ` dodji at gcc dot gnu dot org
2009-11-29  4:09 ` hjl dot tools at gmail dot com
2009-11-29 19:19 ` dodji at gcc dot gnu dot org
2009-11-29 20:43 ` dodji 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=20080801140545.3279.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).