public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/101029] [10/11/12 regression] unexpected error: non-constant condition for static assertion in gcc 10/11, but not 9 (clang also fine)
Date: Sat, 12 Jun 2021 16:40:53 +0000	[thread overview]
Message-ID: <bug-101029-4-tEKJTlTlYF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101029-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jason Merrill <jason@gcc.gnu.org>:

https://gcc.gnu.org/g:08e1ff9d6e5a419d5b4a60c077df549e81601d9b

commit r12-1404-g08e1ff9d6e5a419d5b4a60c077df549e81601d9b
Author: Jason Merrill <jason@redhat.com>
Date:   Fri Jun 11 16:55:30 2021 -0400

    c++: constexpr and array[0] [PR101029]

    build_vec_init_elt exits early if we're initializing a zero-element array,
    so build_vec_init needs to do the same to avoid trying to instantiate
things
    after we've already started throwing important bits away.

            PR c++/101029

    gcc/cp/ChangeLog:

            * init.c (build_vec_init): Shortcut [0] case.

    gcc/testsuite/ChangeLog:

            * g++.dg/ext/array4.C: New test.

  parent reply	other threads:[~2021-06-12 16:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-11 12:04 [Bug c++/101029] New: " jim.w.walker at gmail dot com
2021-06-11 12:05 ` [Bug c++/101029] " jim.w.walker at gmail dot com
2021-06-11 12:17 ` marxin at gcc dot gnu.org
2021-06-11 12:22 ` redi at gcc dot gnu.org
2021-06-11 13:41 ` marxin at gcc dot gnu.org
2021-06-11 13:42 ` marxin at gcc dot gnu.org
2021-06-11 20:45 ` jason at gcc dot gnu.org
2021-06-11 22:20 ` [Bug c++/101029] [10/11/12 regression] " jason at gcc dot gnu.org
2021-06-12 16:40 ` cvs-commit at gcc dot gnu.org [this message]
2021-06-16  9:03 ` jim.w.walker at gmail dot com
2021-06-16  9:16 ` redi at gcc dot gnu.org
2021-06-16 18:33 ` cvs-commit at gcc dot gnu.org
2021-06-17  3:38 ` cvs-commit at gcc dot gnu.org
2021-06-17  3:39 ` cvs-commit at gcc dot gnu.org
2021-06-17  3:39 ` cvs-commit at gcc dot gnu.org
2021-07-06  6:49 ` 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-101029-4-tEKJTlTlYF@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).