From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Jakub Rachucki <jrachucki@n7space.com>
Cc: "libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>
Subject: Re: Checking libstdcxx coverage
Date: Thu, 10 Nov 2022 15:55:58 +0000 [thread overview]
Message-ID: <CAH6eHdQd_VZ0a0LqJ-ODfVBiioC_=bMTmLB3hTDZkKV=8XG_AQ@mail.gmail.com> (raw)
In-Reply-To: <DB7PR03MB48596D3C2FDCF97B888F6372EE019@DB7PR03MB4859.eurprd03.prod.outlook.com>
On Thu, 10 Nov 2022 at 15:53, Jakub Rachucki via Libstdc++
<libstdc++@gcc.gnu.org> wrote:
> Is there an official way of generating coverage information for libstdc++-v3?
No. You could try adding the flags via the --enable-cxx-flags option
which specifies the flags to use when compiling libstdc++.so
next prev parent reply other threads:[~2022-11-10 15:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 15:53 Jakub Rachucki
2022-11-10 15:55 ` Jonathan Wakely [this message]
2022-11-10 16:00 ` Jakub Rachucki
2022-11-16 16:12 ` Jakub Rachucki
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='CAH6eHdQd_VZ0a0LqJ-ODfVBiioC_=bMTmLB3hTDZkKV=8XG_AQ@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=jrachucki@n7space.com \
--cc=libstdc++@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).