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++/111132] [11/12/13/14 Regression] Function redeclaration in local scope breaks constant expression evaluation
Date: Thu, 24 Aug 2023 18:29:07 +0000	[thread overview]
Message-ID: <bug-111132-4-Fp9nx4mJx5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111132-4@http.gcc.gnu.org/bugzilla/>

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
      Known to work|                            |8.5.0
      Known to fail|                            |9.1.0
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |NEW
           Keywords|                            |needs-bisection
            Summary|Function redeclaration in   |[11/12/13/14 Regression]
                   |local scope breaks constant |Function redeclaration in
                   |expression evaluation       |local scope breaks constant
                   |                            |expression evaluation
   Last reconfirmed|                            |2023-08-24

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Confirmed.

This used to mostly worked in GCC 8.5.0 and before.

In GCC 8.5.0 and before GCC would produce a bogus warning but the static_assert
would worked.

<source>:7:20: warning: inline function 'constexpr bool bar()' used but never
defined
     constexpr bool bar(void);
                    ^~~

  reply	other threads:[~2023-08-24 18:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-24 12:54 [Bug c++/111132] New: " fchelnokov at gmail dot com
2023-08-24 18:29 ` pinskia at gcc dot gnu.org [this message]
2023-08-24 19:54 ` [Bug c++/111132] [11/12/13/14 Regression] " ppalka at gcc dot gnu.org
2023-10-17 10:27 ` rguenth at gcc dot gnu.org
2024-03-07 23:23 ` law at gcc dot gnu.org
2024-04-01 23:18 ` mpolacek at gcc dot gnu.org
2024-04-05 13:11 ` cvs-commit at gcc dot gnu.org
2024-04-05 13:26 ` [Bug c++/111132] [11/12/13 " mpolacek 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-111132-4-Fp9nx4mJx5@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).