From: Jakub Rachucki <jrachucki@n7space.com>
To: "libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>
Subject: Checking libstdcxx coverage
Date: Thu, 10 Nov 2022 15:53:06 +0000 [thread overview]
Message-ID: <DB7PR03MB48596D3C2FDCF97B888F6372EE019@DB7PR03MB4859.eurprd03.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1397 bytes --]
Dear all,
I am trying to check the coverage of the libstdc++. Is it possible to configure the build system to include coverage information only for libstdc++? So far, I have tried to configure the build system of the whole gcc using the --enable-coverage option and then run tests. Here is the complete configuration command:
../gcc/configure --prefix /home/jakub/gcc_install --enable-languages=c,c++ --disable-multilib --enable-coverage --disable-bootstrap
I build the GCC using:
make -j6
and run tests using:
make -k -j6 check
Running the test takes a very long time, most probably because of enabling the coverage flags for the whole GCC not only the C++ library. What's more, .gcno and .gcda files were not generated for libstdc++-v3.
I have also tried to run the libstdc++ test using :
make check-target-libstdc++-v3
or to enter the gcc-build-dir/x86_64-pc-linux-gnu/libstdc++-v3/ directory and run from there:
make -k check
In every case no coverage data is produced for libstdc++-v3.
I tried to manually include coverage flags in configure.ac and Makefile.am files. In this case coverage information were included. Nevertheless, the gcc build system is quite large and complex and I am not sure whether I have included the coverage flags in every needed place.
Is there an official way of generating coverage information for libstdc++-v3?
Best regards,
Jakub
next reply other threads:[~2022-11-10 15:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 15:53 Jakub Rachucki [this message]
2022-11-10 15:55 ` Jonathan Wakely
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=DB7PR03MB48596D3C2FDCF97B888F6372EE019@DB7PR03MB4859.eurprd03.prod.outlook.com \
--to=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).