From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>, cocci@inria.fr
Cc: Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [cocci] Checking software run time characteristics
Date: Fri, 7 Feb 2025 08:43:33 +0100 [thread overview]
Message-ID: <9bfe9c42-ef0c-44ae-a71b-26207e9083ad@web.de> (raw)
In-Reply-To: <ca7c1a14-522a-9c2c-4f85-2fda289b83e8@inria.fr>
> You can try --profile to find out what it is spending the most time on.
Would you like to clarify measurement data (like the following) any further?
Markus_Elfring@Sonne:…/Projekte/Coccinelle/Probe> time spatch --profile delete_statement1-Johannes_Berg.cocci extract-ieee80211_get_mbssid_beacon_len-20250206.h
…
diff =
warning: rule starting on line 4, node 52: [fortrue][1,2,17,18,19] in ieee80211_get_mbssid_beacon_len may be inconsistently modified
warning: rule starting on line 4, node 55: statement[1,2,17,18,19,20] in ieee80211_get_mbssid_beacon_len may be inconsistently modified
warning: rule starting on line 4, node 30: [fortrue][1,2,6,7,9,10,12] in ieee80211_get_mbssid_beacon_len may be inconsistently modified
warning: rule starting on line 4, node 33: statement[1,2,6,7,9,10,12,13] in ieee80211_get_mbssid_beacon_len may be inconsistently modified
warning: rule starting on line 4, node 51: for[1,2,17,18,19]* in ieee80211_get_mbssid_beacon_len may be inconsistently modified
warning: rule starting on line 4, node 29: for[1,2,6,7,9,10,12]* in ieee80211_get_mbssid_beacon_len may be inconsistently modified
…
Note: processing took 1083.7s: extract-ieee80211_get_mbssid_beacon_len-20250206.h
---------------------
profiling result
---------------------
Main total : 1083.707616 sec 1 count
Main.outfiles computation : 1083.691804 sec 1 count
full_engine : 1083.691654 sec 1 count
bigloop : 1083.679190 sec 1 count
Rule rule starting on line 4 : 1083.679188 sec 1 count
process_a_ctl_a_env_a_toplevel : 1083.676273 sec 1 count
mysat : 1083.676131 sec 1 count
ctl : 1083.674814 sec 35 count
pre_engine : 0.015786 sec 1 count
parse cocci : 0.015455 sec 1 count
show_xxx : 0.010977 sec 11 count
HACK : 0.010574 sec 5 count
Common.full_charpos_to_pos : 0.002770 sec 2 count
C unparsing : 0.001845 sec 2 count
Parsing: 1st pass : 0.000956 sec 8 count
YACC : 0.000933 sec 8 count
C parsing.fix_define : 0.000724 sec 5 count
C parsing.lex_ident : 0.000611 sec 1418 count
LEXING : 0.000462 sec 4 count
flow : 0.000359 sec 4 count
C parsing.fix_cpp : 0.000349 sec 4 count
MACRO mgmt prep 1 : 0.000301 sec 4 count
asttoctl2 : 0.000281 sec 1 count
TAC.annotate_program : 0.000257 sec 2 count
C parsing.lookahead : 0.000182 sec 546 count
C consistencycheck : 0.000140 sec 4 count
Transformation3.transform : 0.000127 sec 1 count
Type_c.type_of_s : 0.000085 sec 23 count
Common.info_from_charpos : 0.000070 sec 2 count
worth_trying : 0.000058 sec 1 count
fix_flow : 0.000051 sec 2 count
C parsing.mk_info_item : 0.000050 sec 8 count
Common.=~ : 0.000043 sec 6 count
MACRO mgmt prep 2 : 0.000017 sec 4 count
Main.result analysis : 0.000010 sec 1 count
TAC.typedef_fix : 0.000009 sec 58 count
TAC.add_binding : 0.000008 sec 10 count
C parsing : 0.000006 sec 4 count
check_duplicate : 0.000006 sec 1 count
post_engine : 0.000006 sec 1 count
Main.infiles computation : 0.000001 sec 1 count
TOTAL : 0.000000 sec 4 count
real 18m3,734s
user 18m1,192s
sys 0m1,021s
Regards,
Markus
next prev parent reply other threads:[~2025-02-07 7:44 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 9:31 [cocci] possible regressions in 1.1.1 -> 1.2 Johannes Berg
2025-02-06 9:48 ` Johannes Berg
2025-02-06 9:53 ` Victor Gambier
2025-02-06 10:00 ` Johannes Berg
2025-02-06 12:36 ` Markus Elfring
2025-02-06 9:59 ` Julia Lawall
2025-02-06 10:07 ` Johannes Berg
2025-02-06 10:12 ` Johannes Berg
2025-02-06 13:34 ` Markus Elfring
2025-02-06 10:13 ` Julia Lawall
2025-02-06 10:17 ` Johannes Berg
2025-02-06 13:46 ` Markus Elfring
2025-02-06 13:00 ` Markus Elfring
2025-02-06 16:50 ` Markus Elfring
2025-02-08 11:26 ` [cocci] Checking SmPL test cases? Markus Elfring
2025-02-08 11:58 ` Julia Lawall
2025-02-08 12:51 ` Markus Elfring
2025-02-08 14:28 ` Markus Elfring
2025-02-08 15:43 ` Julia Lawall
2025-02-09 8:42 ` Markus Elfring
2025-02-07 7:43 ` Markus Elfring [this message]
2025-02-07 7:55 ` [cocci] Checking software run time characteristics Julia Lawall
2025-02-07 8:15 ` Markus Elfring
2025-02-07 8:59 ` Johannes Berg
2025-02-07 9:50 ` Markus Elfring
2025-02-11 9:58 ` [cocci] possible regressions in 1.1.1 -> 1.2 Victor Gambier
2025-02-11 10:33 ` [cocci] Comparing software run time characteristics Markus Elfring
2025-02-12 9:52 ` [cocci] Profiling of SmPL code? Markus Elfring
2026-03-27 10:43 ` [cocci] possible regressions in 1.1.1 -> 1.2 Victor Gambier
2026-03-27 10:49 ` Johannes Berg
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=9bfe9c42-ef0c-44ae-a71b-26207e9083ad@web.de \
--to=markus.elfring@web.de \
--cc=cocci@inria.fr \
--cc=johannes@sipsolutions.net \
--cc=julia.lawall@inria.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.