public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/95197] New: libgomp/testsuite/libgomp.c++/for-27.C fails with -std=c++17
Date: Tue, 19 May 2020 00:14:11 +0000 [thread overview]
Message-ID: <bug-95197-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95197
Bug ID: 95197
Summary: libgomp/testsuite/libgomp.c++/for-27.C fails with
-std=c++17
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: mpolacek at gcc dot gnu.org
Target Milestone: ---
See <https://gcc.gnu.org/pipermail/gcc-patches/2020-May/545879.html> for why
this fails. My workaround was
--- a/libgomp/testsuite/libgomp.c++/for-27.C
+++ b/libgomp/testsuite/libgomp.c++/for-27.C
@@ -151,6 +151,12 @@ f4 (const I<int> &x, const I<int> &y)
else if (results[i]) \
abort ()
+// FIXME: OpenMP seems to count on this being instantiated; the copy
+// constructor is called in functions fn2/fn3/fn4. But in C++17 we
+// elide this copy constructor, so it's never been instantiated. For
+// now instantiate it explicitly.
+template I<int>::I(const I<int> &);
+
int
main ()
{
Seems that OpenMP has to call mark_used or some such.
next reply other threads:[~2020-05-19 0:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 0:14 mpolacek at gcc dot gnu.org [this message]
2020-05-25 14:23 ` [Bug c++/95197] " jakub at gcc dot gnu.org
2020-05-25 14:38 ` jakub at gcc dot gnu.org
2020-05-25 16:55 ` jakub at gcc dot gnu.org
2020-05-26 7:39 ` cvs-commit at gcc dot gnu.org
2020-06-14 10:07 ` cvs-commit 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-95197-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).