public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/60708] [4.8/4.9 Regression] An array temporary causes an ICE in gimplify
Date: Mon, 31 Mar 2014 08:24:00 -0000	[thread overview]
Message-ID: <bug-60708-4-JTE833t7rW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60708-4@http.gcc.gnu.org/bugzilla/>

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
      Known to work|                            |4.7.3
           Keywords|                            |accepts-invalid
   Last reconfirmed|                            |2014-03-31
     Ever confirmed|0                           |1
            Summary|An array temporary causes   |[4.8/4.9 Regression] An
                   |an ICE in gimplify          |array temporary causes an
                   |                            |ICE in gimplify
   Target Milestone|---                         |4.8.3
      Known to fail|                            |4.8.0

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
With 4.7 I get the maybe informative

t.ii:5:55: error: 'my_make_pair' function uses 'auto' type specifier without
trailing return type
t.ii: In instantiation of 'mypair<T*, int> S<T>::get_pair() [with T = char]':
t.ii:23:19:   required from here
t.ii:12:36: error: 'my_make_pair' was not declared in this scope
t.ii:23: confused by earlier errors, bailing out

thus we miss the error in 4.8.x and 4.9 (but ICE the same later).

Marking as accepts-invalid regression.  After that it would be an
error-recovery
ice-on-invalid.


  reply	other threads:[~2014-03-31  8:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-30 13:29 [Bug c++/60708] New: " ville.voutilainen at gmail dot com
2014-03-31  8:24 ` rguenth at gcc dot gnu.org [this message]
2014-03-31  8:24 ` [Bug c++/60708] [4.8/4.9 Regression] " rguenth at gcc dot gnu.org
2014-03-31  8:27 ` ville.voutilainen at gmail dot com
2014-03-31 12:54 ` ville.voutilainen at gmail dot com
2014-04-01 18:10 ` jason at gcc dot gnu.org
2014-04-01 19:14 ` jason at gcc dot gnu.org
2014-04-01 19:17 ` [Bug c++/60708] [4.8 " jason at gcc dot gnu.org
2014-05-13 16:05 ` jason at gcc dot gnu.org
2014-05-13 16:07 ` jason at gcc dot gnu.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=bug-60708-4-JTE833t7rW@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).