From: mstefani@redhat.com (Michael Stefaniuc)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Wrong --parse-c stats
Date: Thu, 07 Feb 2013 22:46:39 +0100 [thread overview]
Message-ID: <511420BF.50704@redhat.com> (raw)
Hello,
not sure if somebody is interested: while running --parse-c on the Wine
source I've noticed impossible stats for 3 C files. As those are test
files those are heavy macro (ab)users.
dlls/quartz/tests/dsoundrender.c
http://source.winehq.org/git/wine.git/blob_plain/HEAD:/dlls/quartz/tests/dsoundrender.c
NB total files = 1; perfect = 0; pbs = 0; timeout = 0; =========> 0%
nb good = 1124, nb passed = 25 =========> 2.224199% passed
nb good = 1124, nb bad = -891 =========> 482.403433% good
dlls/quartz/tests/videorenderer.c
http://source.winehq.org/git/wine.git/blob_plain/HEAD:/dlls/quartz/tests/videorenderer.c
NB total files = 1; perfect = 0; pbs = 0; timeout = 0; =========> 0%
nb good = 522, nb passed = 20 =========> 3.831418% passed
nb good = 522, nb bad = -358 =========> 318.292683% good
dlls/msxml3/tests/domdoc.c
http://source.winehq.org/git/wine.git/blob_plain/HEAD:/dlls/msxml3/tests/domdoc.c
NB total files = 1; perfect = 0; pbs = 0; timeout = 0; =========> 0%
nb good = 135789, nb passed = 1051 =========> 0.773995% passed
nb good = 135789, nb bad = -124421 =========> 1194.484518% good
I was using my Wine macro file
http://people.redhat.com/mstefani/wine/coccinelle/macros for the above
runs. For the quartz files it doesn't makes much difference to run
without a --macros-file but the msxml3 test file gives a different
interesting result:
dlls/msxml3/tests/domdoc.c
NB total files = 1; perfect = 0; pbs = 1; timeout = 0; =========> 0%
nb good = 0, nb passed = 168 =========> inf% passed
nb good = 0, nb bad = 3250 =========> 0.000000% good
bye
michael
next reply other threads:[~2013-02-07 21:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 21:46 Michael Stefaniuc [this message]
2013-02-08 6:06 ` [Cocci] Wrong --parse-c stats Julia Lawall
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=511420BF.50704@redhat.com \
--to=mstefani@redhat.com \
--cc=cocci@systeme.lip6.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.