public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/95468] [8/9/10/11 Regression] ICE in expression sfinae
Date: Wed, 03 Jun 2020 15:23:59 +0000	[thread overview]
Message-ID: <bug-95468-4-INi4Dzrvkq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95468-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95468

Patrick Palka <ppalka at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jason at gcc dot gnu.org,
                   |                            |ppalka at gcc dot gnu.org
            Summary|ICE in expression sfinae    |[8/9/10/11 Regression] ICE
                   |                            |in expression sfinae
           Keywords|ice-on-invalid-code         |ice-on-valid-code
   Target Milestone|---                         |8.5

--- Comment #2 from Patrick Palka <ppalka at gcc dot gnu.org> ---
(In reply to kab from comment #1)
> This was labeled as "ice-on-invalid-code".  Am I missing something?  I don't
> see anything invalid here.

I just now adjusted the label to be "ice-on-valid-code" instead.

This seems to be a regression relative to GCC 4.8, which compiles the testcase
successfully (with -std=c++11).  We began ICEing on the testcase starting with
r0-122271.

Here is a reduced testcase:

template <int> struct a { };

struct c {
  template <int d> static constexpr bool condition() { return d; }
};

template<typename>
void foo() {
  using A = a<c::condition<bool(true)>()>;
}

void bar() {
  foo<int>();
}

  parent reply	other threads:[~2020-06-03 15:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-01 19:57 [Bug c++/95468] New: " kab at acm dot org
2020-06-02  5:56 ` [Bug c++/95468] " marxin at gcc dot gnu.org
2020-06-03  1:09 ` kab at acm dot org
2020-06-03 15:23 ` ppalka at gcc dot gnu.org [this message]
2020-06-03 15:48 ` [Bug c++/95468] [8/9/10/11 Regression] " ppalka at gcc dot gnu.org
2021-01-14  8:57 ` rguenth at gcc dot gnu.org
2021-02-12 23:37 ` ppalka at gcc dot gnu.org
2021-02-23 14:40 ` cvs-commit at gcc dot gnu.org
2021-02-23 14:42 ` [Bug c++/95468] [8/9/10 " ppalka at gcc dot gnu.org
2021-03-31 12:33 ` cvs-commit at gcc dot gnu.org
2021-04-21 21:09 ` [Bug c++/95468] [8/9 " cvs-commit at gcc dot gnu.org
2021-05-14 13:58 ` [Bug c++/95468] [8 " jakub 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-95468-4-INi4Dzrvkq@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).