public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "michael.kenzel at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/113580] New: -Wunused-parameter in template imported from module causes segmentation fault
Date: Wed, 24 Jan 2024 11:57:26 +0000	[thread overview]
Message-ID: <bug-113580-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 113580
           Summary: -Wunused-parameter in template imported from module
                    causes segmentation fault
           Product: gcc
           Version: 13.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: michael.kenzel at gmail dot com
  Target Milestone: ---

The following example will reproduce the issue:

        // A.ixx
        export module A;

        export void fun(auto&& x) {}

        // main.cpp
        import A;

        int main()
        {
                fun(42);
        }


g++ -std=c++23 -fmodules-ts -c -x c++ A.ixx
g++ -std=c++23 -Wunused-parameter -fmodules-ts main.cpp A.o 

results in

Segmentation fault
0x7ff37686550f ???
        ./signal/../sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0
0x7ff37697e159 __strlen_avx2
        ../sysdeps/x86_64/multiarch/strlen-avx2.S:76
0x7ff3768506c9 __libc_start_call_main
        ../sysdeps/nptl/libc_start_call_main.h:58
0x7ff376850784 __libc_start_main_impl
        ../csu/libc-start.c:360

             reply	other threads:[~2024-01-24 11:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-24 11:57 michael.kenzel at gmail dot com [this message]
2024-01-26 22:29 ` [Bug c++/113580] " cvs-commit at gcc dot gnu.org
2024-01-26 22:38 ` nshead at gcc dot gnu.org
2024-03-06 14:00 ` 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-113580-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).