public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "slyfox at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/114933] New: [15 Regression] mcfgthread-1.6.1 typecheck failure: error: explicit specializations are not permitted here
Date: Fri, 03 May 2024 08:54:19 +0000	[thread overview]
Message-ID: <bug-114933-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 114933
           Summary: [15 Regression] mcfgthread-1.6.1 typecheck failure:
                    error: explicit specializations are not permitted here
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: slyfox at gcc dot gnu.org
  Target Milestone: ---

mcfgthread-1.6.1 build failure started happening a few days ago on `gcc`
`master`. On r15-116-gff4dc8b10a421c minimized example failure looks this way:

    // $ cat a.cc
    extern "C++" template<bool> struct __MCF_static_assert;
    extern "C++" template<> struct __MCF_static_assert<true> { };

Fails as:

$ g++ -c a.cc -std=c++20
a.cc:2:14: error: explicit specializations are not permitted here
    2 | extern "C++" template<> struct __MCF_static_assert<true> { };
      |              ^~~~~~~~~~

For comparison 13.2.0 builds the example successfully:

$ g++-13.2.0 -c a.cc -std=c++20
<ok>

Compiler details:

$ g++ -v |& unnix
Using built-in specs.
COLLECT_GCC=/<<NIX>>/gcc-15.0.0/bin/g++
COLLECT_LTO_WRAPPER=/<<NIX>>/gcc-15.0.0/libexec/gcc/x86_64-unknown-linux-gnu/15.0.0/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with: ../source/configure --prefix=/<<NIX>>/gcc-15.0.0
--with-gmp-include=/<<NIX>>/gmp-6.3.0-dev/include
--with-gmp-lib=/<<NIX>>/gmp-6.3.0/lib
--with-mpfr-include=/<<NIX>>/mpfr-4.2.1-dev/include
--with-mpfr-lib=/<<NIX>>/mpfr-4.2.1/lib --with-mpc=/<<NIX>>/libmpc-1.3.1
--with-native-system-header-dir=/<<NIX>>/glibc-2.39-31-dev/include
--with-build-sysroot=/
--with-gxx-include-dir=/<<NIX>>/gcc-15.0.0/include/c++/15.0.0/
--program-prefix= --enable-lto --disable-libstdcxx-pch
--without-included-gettext --with-system-zlib --enable-checking=release
--enable-static --enable-languages=c,c++ --disable-multilib --enable-plugin
--disable-libcc1 --with-isl=/<<NIX>>/isl-0.20 --disable-bootstrap
--build=x86_64-unknown-linux-gnu --host=x86_64-unknown-linux-gnu
--target=x86_64-unknown-linux-gnu
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 15.0.0 99999999 (experimental) (GCC)

             reply	other threads:[~2024-05-03  8:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-03  8:54 slyfox at gcc dot gnu.org [this message]
2024-05-03  9:05 ` [Bug c++/114933] " slyfox at gcc dot gnu.org
2024-05-03  9:07 ` pinskia at gcc dot gnu.org
2024-05-03  9:09 ` pinskia at gcc dot gnu.org
2024-05-03  9:10 ` pinskia at gcc dot gnu.org
2024-05-03  9:12 ` pinskia at gcc dot gnu.org
2024-05-03  9:14 ` lh_mouse at 126 dot com
2024-05-03  9:17 ` pinskia at gcc dot gnu.org
2024-05-03  9:50 ` lh_mouse at 126 dot com
2024-05-03 20:49 ` slyfox 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-114933-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).