From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: "Jørgen Kvalsvik" <jorgen.kvalsvik@woven-planet.global>,
gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Add condition coverage profiling
Date: Fri, 22 Apr 2022 07:37:54 +0200 [thread overview]
Message-ID: <14a74c2a-6131-294c-01b5-513bd76f4f52@embedded-brains.de> (raw)
In-Reply-To: <67e557c7-f03e-9c0b-faf1-fefbecddcac6@woven-planet.global>
On 17/04/2022 13:27, Jørgen Kvalsvik wrote:
>> In theory, would it be possible to print the state of the truth table with the
>> information available in the gcda and gcno files? For example:
>>
>> Truth table for: a && (b || c)) && d
>>
>> 0 | 1 | 2 | 3 || covered
>> --+---+---+---++--------
>> 0 | X | X | X || Y
>> 0 | X | X | X || Y
>> 0 | X | X | X || Y
>> 0 | X | X | X || Y
>> 0 | X | X | X || Y
>> 0 | X | X | X || Y
>> 0 | X | X | X || Y
>> 0 | X | X | X || Y
>> 1 | 0 | 0 | X || N
>> 1 | 0 | 0 | X || N
>> 1 | 0 | 1 | 0 || N
>> 1 | 0 | 1 | 1 || N
>> 1 | 1 | X | 0 || Y
>> 1 | 1 | X | 0 || Y
>> 1 | 1 | X | 1 || Y
>> 1 | 1 | X | 1 || Y
> Maybe? We would at least need to store the masking tables too, which right now
> are implicitly stored as in the instrumentation. It's not too bad, but it
> probably means the two functions should return some richer structure, which in
> turn means a little bit of redesign. Computing the truth table itself shouldn't
> be difficult.
Using the tool in the context of safety-critical application would
normally require also a tool qualification. For GCC, this is a bit
unrealistic. It would help if the tool output can be verified. Being
able to inspect the masking tables could help a reviewer to check what
the tool did for a sample set of inputs.
--
embedded brains GmbH
Herr Sebastian HUBER
Dornierstr. 4
82178 Puchheim
Germany
email: sebastian.huber@embedded-brains.de
phone: +49-89-18 94 741 - 16
fax: +49-89-18 94 741 - 08
Registergericht: Amtsgericht München
Registernummer: HRB 157899
Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
Unsere Datenschutzerklärung finden Sie hier:
https://embedded-brains.de/datenschutzerklaerung/
next prev parent reply other threads:[~2022-04-22 5:37 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 11:55 Jørgen Kvalsvik
2022-03-24 16:08 ` Martin Liška
2022-03-25 19:44 ` Jørgen Kvalsvik
2022-03-28 13:39 ` Martin Liška
2022-03-28 13:52 ` Jørgen Kvalsvik
2022-03-28 14:40 ` Jørgen Kvalsvik
2022-04-07 12:04 ` Martin Liška
2022-04-19 14:22 ` Jørgen Kvalsvik
2022-04-07 16:53 ` Sebastian Huber
2022-04-08 7:28 ` Jørgen Kvalsvik
2022-04-08 7:33 ` Jørgen Kvalsvik
2022-04-08 8:50 ` Sebastian Huber
2022-04-04 8:14 ` Sebastian Huber
2022-04-05 7:04 ` Sebastian Huber
2022-04-05 20:07 ` Jørgen Kvalsvik
2022-04-06 7:35 ` Sebastian Huber
2022-04-17 11:27 ` Jørgen Kvalsvik
2022-04-22 5:37 ` Sebastian Huber [this message]
2022-04-22 10:13 ` Jørgen Kvalsvik
2022-07-08 13:45 ` Sebastian Huber
2022-07-11 7:26 ` Jørgen Kvalsvik
2022-07-11 10:02 Jørgen Kvalsvik
2022-07-12 14:05 ` Sebastian Huber
2022-07-13 2:04 ` Jørgen Kvalsvik
2022-07-15 11:39 Jørgen Kvalsvik
2022-07-15 11:47 ` Jørgen Kvalsvik
2022-07-15 13:31 ` Sebastian Huber
2022-07-15 13:47 ` Jørgen Kvalsvik
2022-08-02 7:58 ` Jørgen Kvalsvik
2022-08-04 7:43 ` Sebastian Huber
2022-08-04 9:13 ` Jørgen Kvalsvik
2022-10-12 10:16 Jørgen Kvalsvik
2022-10-18 0:17 ` Hans-Peter Nilsson
2022-10-18 10:13 ` Jørgen Kvalsvik
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=14a74c2a-6131-294c-01b5-513bd76f4f52@embedded-brains.de \
--to=sebastian.huber@embedded-brains.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=jorgen.kvalsvik@woven-planet.global \
/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).