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++/93431] FAIL: g++.dg/cpp2a/lambda-uneval9.C -std=c++2a (test for excess errors)
Date: Thu, 07 May 2020 13:56:07 +0000 [thread overview]
Message-ID: <bug-93431-4-iirDCjrE5N@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-93431-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93431
Thomas Schwinge <tschwinge at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed|2020-01-27 00:00:00 |2020-5-7
Target|hppa2.0w-hp-hpux11.11 |hppa2.0w-hp-hpux11.11 nvptx
CC| |tschwinge at gcc dot gnu.org
--- Comment #3 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
Supposedly same issue for nvptx target, where as of somewhere in
cff5a231480526aa73094a22fe8b2f39b63735a4..c416c52bcdb120db5e8c53a51bd78c4360daf79b
we got the regression:
UNSUPPORTED: g++.dg/cpp2a/lambda-uneval9.C -std=c++98
UNSUPPORTED: g++.dg/cpp2a/lambda-uneval9.C -std=c++14
UNSUPPORTED: g++.dg/cpp2a/lambda-uneval9.C -std=c++17
PASS: g++.dg/cpp2a/lambda-uneval9.C -std=c++2a (test for excess errors)
[-PASS:-]{+FAIL:+} g++.dg/cpp2a/lambda-uneval9.C -std=c++2a execution test
spawn [...]/nvptx-none-run-single ./lambda-uneval9.exe
error : Multiple definition of '_ZZ7counterIZ1fvEUlvE_EivE3cnt' in 'input
file 2 at offset 4789', first defined in 'input file 1 at offset 1796'
nvptx-run: cuLinkAddData failed: unknown error (CUDA_ERROR_UNKNOWN, 999)
next prev parent reply other threads:[~2020-05-07 13:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-93431-4@http.gcc.gnu.org/bugzilla/>
2020-03-30 23:35 ` danglin at gcc dot gnu.org
2020-05-07 13:56 ` tschwinge at gcc dot gnu.org [this message]
2023-11-15 18:56 ` tschwinge 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-93431-4-iirDCjrE5N@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).