public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/104620] FAIL: g++.dg/cpp23/consteval-if2.C  -std=gnu++20  (test for errors)
Date: Thu, 24 Mar 2022 14:29:24 +0000	[thread overview]
Message-ID: <bug-104620-4-JfyqzC7brr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104620-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Patrick Palka <ppalka at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #4)
> This one is valid, but before your r12-7264 was incorrectly rejected because
> 8 * baz (0) etc. is wrapped in NON_DEPENDENT_EXPR,
> potential_constant_expression_1 recursed on the NON_DEPENDENT_EXPR operand,
> found it is ok but cxx_eval_constant_expression
> rejected the NON_DEPENDENT_EXPR.

Makes sense, similar to the #2 case in comment #5.

> Bet for the build_over_call
> processing_template_decl immediate_invocation_p code we need to punt
> silently if there is something we can't handle but fail loudly if we can
> handle everything but it is clearly always not a constant expression. 
> potential_constant_expression_1 isn't 100% accurate, there are cases where
> it gets stuff through.

IIUC as long as NON_DEPENDENT_EXPR doesn't appear inside a non-dependent
consteval call then we'll currently correctly accept/reject it ahead of time,
e.g.:

consteval int foo(int x) { return x; }

template<class>
void bar(int x)
{
  constexpr int y = 0;
  foo(x);     // error: 'x' is not a constant expression
  foo(y);     // OK
  foo(x * 1); // no (ahead of time) error due to NON_DEPENDENT_EXPR
}

  parent reply	other threads:[~2022-03-24 14:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-21 19:38 [Bug c++/104620] New: " danglin at gcc dot gnu.org
2022-03-23 18:04 ` [Bug c++/104620] " mpolacek at gcc dot gnu.org
2022-03-23 18:42 ` mpolacek at gcc dot gnu.org
2022-03-23 20:35 ` ppalka at gcc dot gnu.org
2022-03-24 12:21 ` jakub at gcc dot gnu.org
2022-03-24 13:29 ` jakub at gcc dot gnu.org
2022-03-24 13:31 ` ppalka at gcc dot gnu.org
2022-03-24 13:37 ` ppalka at gcc dot gnu.org
2022-03-24 14:29 ` ppalka at gcc dot gnu.org [this message]
2022-03-24 15:21 ` jason at gcc dot gnu.org
2022-03-24 15:42 ` cvs-commit at gcc dot gnu.org
2022-03-24 17:19 ` ppalka at gcc dot gnu.org
2022-03-26 23:01 ` jason at gcc dot gnu.org
2022-05-06  8:32 ` jakub at gcc dot gnu.org
2023-05-08 12:23 ` 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-104620-4-JfyqzC7brr@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).