public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/99700] uninitialized variable accepted as a constant expression in C++ 20
Date: Thu, 15 Apr 2021 00:14:19 +0000	[thread overview]
Message-ID: <bug-99700-4-opyY8thpzC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99700-4@http.gcc.gnu.org/bugzilla/>

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

Martin Sebor <msebor at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |msebor at gcc dot gnu.org
            Summary|gcc takes an uninitialized  |uninitialized variable
                   |variable as a constant      |accepted as a constant
                   |expression                  |expression in C++ 20
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2021-04-15

--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
Confirmed with -std=c++20.  In earlier modes GCC rejects the test case as
expected.

$ (set -x && gcc -O2 -S -Wall -std=c++20 pr99700.C && gcc -O2 -S -Wall
-std=c++17 pr99700.C)
+ gcc -O2 -S -Wall -std=c++20 pr99700.C
+ gcc -O2 -S -Wall -std=c++17 pr99700.C
pr99700.C: In constructor ‘constexpr A::A()’:
pr99700.C:2:29: error: member ‘A::c’ must be initialized by mem-initializer in
‘constexpr’ constructor
    2 |   constexpr A() { c[0] = 0; }
      |                             ^
pr99700.C:3:8: note: declared here
    3 |   char c[2];
      |        ^
pr99700.C: At global scope:
pr99700.C:6:13: error: ‘constexpr A::A()’ called in a constant expression
    6 | constexpr A a;
      |             ^
pr99700.C:2:13: note: ‘constexpr A::A()’ declared here
    2 |   constexpr A() { c[0] = 0; }
      |             ^

When reporting bugs please include all the information we ask for here:
https://gcc.gnu.org/bugs/#need.  Links to other sites are not a substitute.

  reply	other threads:[~2021-04-15  0:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-21 18:22 [Bug c++/99700] New: gcc takes an uninitialized variable as a constant expression hewillk at gmail dot com
2021-04-15  0:14 ` msebor at gcc dot gnu.org [this message]
2021-04-15  0:15 ` [Bug c++/99700] [10/11 Regression] uninitialized variable accepted as a constant expression in C++ 20 msebor at gcc dot gnu.org
2021-04-15 16:55 ` ppalka at gcc dot gnu.org
2021-04-16 13:25 ` cvs-commit at gcc dot gnu.org
2021-04-16 13:27 ` [Bug c++/99700] [10 " ppalka at gcc dot gnu.org
2022-05-11 17:07 ` 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-99700-4-opyY8thpzC@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).