From: Jakub Rachucki <jrachucki@n7space.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: "libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>
Subject: RE: Checking libstdcxx coverage
Date: Wed, 16 Nov 2022 16:12:49 +0000 [thread overview]
Message-ID: <DB7PR03MB48590649AE8CE22AE2134215EE079@DB7PR03MB4859.eurprd03.prod.outlook.com> (raw)
In-Reply-To: <DB7PR03MB4859ED84773AFD6CCA5554ECEE019@DB7PR03MB4859.eurprd03.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1315 bytes --]
I have configured, built, and run tests using the "--enable-cxx-flags="--coverage"" flag. But it resulted in almost 0% coverage. I am wondering if --enable-cxx-flags also modifies linker flags? If not, then I think a coverage was measured incorrectly and this is a reason why it is so low. What do you think @Jonathan<mailto:jwakely.gcc@gmail.com>, is there a flag that also affects linker flags?
-----Original Message-----
From: Jakub Rachucki
Sent: 10 November 2022 17:01
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: libstdc++@gcc.gnu.org
Subject: RE: Checking libstdcxx coverage
Ok, thank you Jonathan, I will try it!
-----Original Message-----
From: Jonathan Wakely <jwakely.gcc@gmail.com<mailto:jwakely.gcc@gmail.com>>
Sent: 10 November 2022 16:56
To: Jakub Rachucki <jrachucki@n7space.com<mailto:jrachucki@n7space.com>>
Cc: libstdc++@gcc.gnu.org<mailto:libstdc++@gcc.gnu.org>
Subject: Re: Checking libstdcxx coverage
On Thu, 10 Nov 2022 at 15:53, Jakub Rachucki via Libstdc++ <libstdc++@gcc.gnu.org<mailto: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
prev parent reply other threads:[~2022-11-16 16:12 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
2022-11-10 16:00 ` Jakub Rachucki
2022-11-16 16:12 ` Jakub Rachucki [this message]
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=DB7PR03MB48590649AE8CE22AE2134215EE079@DB7PR03MB4859.eurprd03.prod.outlook.com \
--to=jrachucki@n7space.com \
--cc=jwakely.gcc@gmail.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).