From: "François Dumont" <frs.dumont@gmail.com>
To: gcc@gcc.gnu.org
Subject: Attempt to fix g++.dg tests failures in gnu-versioned-namespace mode
Date: Wed, 20 Sep 2023 07:08:25 +0200 [thread overview]
Message-ID: <602a9594-eb22-117a-0372-9cdbaa0d2672@gmail.com> (raw)
I've configured libstdc++ with --enable-symvers=gnu-versioned-namespace
and run make check-c++.
A number of failures are like this one:
/home/fdumont/dev/gcc/git/gcc/testsuite/g++.dg/coroutines/coro-bad-alloc-00-bad-op-new.C:
In function 'coro1 f()':
/home/fdumont/dev/gcc/git/gcc/testsuite/g++.dg/coroutines/coro-bad-alloc-00-bad-op-new.C:9:1:
error: 'operator new' is provided by
'std::__8::__n4861::__coroutine_traits_impl<coro1, void>::promise_type'
{aka 'co
ro1::promise_type'} but is not usable with the function signature 'coro1
f()'
compiler exited with status 1
FAIL: g++.dg/coroutines/coro-bad-alloc-00-bad-op-new.C (test for
errors, line 9)
FAIL: g++.dg/coroutines/coro-bad-alloc-00-bad-op-new.C (test for excess
errors)
Excess errors:
/home/fdumont/dev/gcc/git/gcc/testsuite/g++.dg/coroutines/coro-bad-alloc-00-bad-op-new.C:9:1:
error: 'operator new' is provided by
'std::__n4861::__coroutine_traits_impl<coro1, void>::promise_type' {aka
'coro1::promise_type'} but is not usable with the function signature
'coro1 f()'
The '__8' is messing with expected output.
So I've added:
# Ignore optional version namespace from libstdc++.
regsub -all "std::__8::" $text "std::" text
in testsuite/lib/prune.exp prune_gcc_output.
But it had no impact, same failures.
What am I missing ?
Thanks,
François
next reply other threads:[~2023-09-20 5:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 5:08 François Dumont [this message]
2023-09-20 7:22 ` Thomas Schwinge
2023-09-21 5:01 ` François Dumont
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=602a9594-eb22-117a-0372-9cdbaa0d2672@gmail.com \
--to=frs.dumont@gmail.com \
--cc=gcc@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).