public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bjoern at hoehrmann dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/105304] New: ICE segfault using ad-hoc concept with -Wall
Date: Mon, 18 Apr 2022 16:14:20 +0000	[thread overview]
Message-ID: <bug-105304-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 105304
           Summary: ICE segfault using ad-hoc concept with -Wall
           Product: gcc
           Version: 11.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: bjoern at hoehrmann dot de
  Target Milestone: ---

GCC 11.2.0 on Linux

 ❯  g++-11 -Wall -std=c++2a -o x ../mini.cxx   
../mini.cxx: In function 'int main()':
../mini.cxx:23:18: internal compiler error: Segmentation fault
   23 |                 }) {
      |                  ^
Please submit a full bug report,

Code:

#include <iostream>
#include <utility>

class X
{
public:
  int m(int, int, int = 7) { return 123; }
};

template<typename... Ts>
void
invoke_m(std::index_sequence_for<Ts...> is)
{
  X o;
  o.m(Ts()...);
}

int
main()
{
  if constexpr (requires {
                  invoke_m<int, int, int, int>(std::make_index_sequence<4>());
                }) {
    std::cerr << "ok" << '\n';
  }

  return 0;
}

Compiles when omitting -Wall.

             reply	other threads:[~2022-04-18 16:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-18 16:14 bjoern at hoehrmann dot de [this message]
2022-04-19 14:13 ` [Bug c++/105304] [10/11/12 Regression] ICE segfault using ad-hoc concept with -Wall since r10-7441-ga7ea3d2ced786c45 marxin at gcc dot gnu.org
2022-04-21  7:22 ` rguenth at gcc dot gnu.org
2022-04-22 18:16 ` ppalka at gcc dot gnu.org
2022-04-26  1:49 ` cvs-commit at gcc dot gnu.org
2022-04-26  1:50 ` [Bug c++/105304] [10/11 " ppalka at gcc dot gnu.org
2022-04-28 15:39 ` cvs-commit at gcc dot gnu.org
2022-05-09 23:33 ` [Bug c++/105304] [10 " cvs-commit at gcc dot gnu.org
2022-05-09 23:35 ` ppalka 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-105304-4@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).