public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/112724] New: C++ "'excess_precision_expr' not supported by dump_expr<expression error>"
Date: Mon, 27 Nov 2023 09:52:22 +0000 [thread overview]
Message-ID: <bug-112724-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112724
Bug ID: 112724
Summary: C++ "'excess_precision_expr' not supported by
dump_expr<expression error>"
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: diagnostic, testsuite-fail
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: tschwinge at gcc dot gnu.org
CC: burnus at gcc dot gnu.org, jakub at gcc dot gnu.org
Target Milestone: ---
(Only) in '-m32' testing of x86_64-pc-linux-gnu, I see (only) for C++ testing
of the test case added in commit
r14-5827-g1802f64e674eeef0c0d7e8f6ca2846145ec16315 "OpenMP: Accept argument to
depobj's destroy clause":
+PASS: c-c++-common/gomp/depobj-3.c -std=c++98 at line 17 (test for
warnings, line 15)
+FAIL: c-c++-common/gomp/depobj-3.c -std=c++98 at line 39 (test for
warnings, line 37)
+PASS: c-c++-common/gomp/depobj-3.c -std=c++98 at line 43 (test for
errors, line 41)
+PASS: c-c++-common/gomp/depobj-3.c -std=c++98 (test for warnings, line
45)
+FAIL: c-c++-common/gomp/depobj-3.c -std=c++98 (test for excess errors)
[...]/c-c++-common/gomp/depobj-3.c: In function 'int main()':
[...]/c-c++-common/gomp/depobj-3.c:37:38: warning: the 'destroy' expression
''excess_precision_expr' not supported by dump_expr<expression error>' should
be the same as the 'depobj' argument 'obj' [-Wopenmp]
This should be:
[...]/c-c++-common/gomp/depobj-3.c:37:38: warning: the 'destroy' expression
'(a + (float)5)' should be the same as the 'depobj' argument 'obj' [-Wopenmp]
next reply other threads:[~2023-11-27 9:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 9:52 tschwinge at gcc dot gnu.org [this message]
2023-11-27 9:53 ` [Bug c++/112724] " tschwinge at gcc dot gnu.org
2023-11-27 10:01 ` rguenth at gcc dot gnu.org
2024-03-22 9:26 ` cvs-commit at gcc dot gnu.org
2024-03-26 9:04 ` cvs-commit at gcc dot gnu.org
2024-03-26 9:11 ` jakub 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-112724-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).