public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/109433] New: [12/13 Regression] ICE with -std=c++11 and static constexpr array inside a template constexpr
Date: Thu, 06 Apr 2023 10:07:36 +0000	[thread overview]
Message-ID: <bug-109433-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 109433
           Summary: [12/13 Regression] ICE with -std=c++11 and static
                    constexpr array inside a template constexpr
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: pinskia at gcc dot gnu.org
  Target Milestone: ---

Note this is not exactly a dup of bug 109431 as it works in GCC 11.3.0.
Note also it ICEs with -std=c++14 in GCC 11.3.0 (which looks to be the same as
PR109431 ) but works with -std=c++11.

testcase:
```
struct RangeLimits
{
    int low = 1;
};

template <int>
int parameterLimits(void)
{
    static RangeLimits constexpr param_limits[ 2 ] = {};
    auto const &limits = param_limits[ 1 ];
    return 0;
}

auto s = parameterLimits<1>();
```

Maybe they are the same issue but I am not 100% sure as they regressed at
different times and produce different ICEs.

The ICE on the trunk:

<source>:10:55: internal compiler error: unexpected expression 'const
RangeLimits()' of kind cast_expr
   10 |     static RangeLimits constexpr param_limits[ 2 ] = {};
      |                                                       ^

             reply	other threads:[~2023-04-06 10:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-06 10:07 pinskia at gcc dot gnu.org [this message]
2023-04-06 10:09 ` [Bug c++/109433] " pinskia at gcc dot gnu.org
2023-04-06 13:06 ` jakub at gcc dot gnu.org
2023-04-06 19:16 ` pinskia at gcc dot gnu.org
2023-05-08 12:26 ` [Bug c++/109433] [12/13/14 " rguenth 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-109433-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).