From: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t 02/12] code_cov_parse_info: do some renames to make it more coherent
Date: Tue, 17 Jan 2023 15:05:57 +0100 [thread overview]
Message-ID: <20230117140607.2759816-3-mauro.chehab@linux.intel.com> (raw)
In-Reply-To: <20230117140607.2759816-1-mauro.chehab@linux.intel.com>
From: Mauro Carvalho Chehab <mchehab@kernel.org>
Let the regex array to be clearer about include regexes, and
coherent with exclude ones.
While here, also rename the file exclude check function, to
have a name closer to its functions counterpart.
No functional changes.
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
---
scripts/code_cov_parse_info | 38 ++++++++++++++++++-------------------
1 file changed, 19 insertions(+), 19 deletions(-)
diff --git a/scripts/code_cov_parse_info b/scripts/code_cov_parse_info
index 1498bd09cdba..d3739211b68a 100755
--- a/scripts/code_cov_parse_info
+++ b/scripts/code_cov_parse_info
@@ -18,10 +18,10 @@ my %all_line;
my %used_source;
my %record;
my %files;
-my @func_regexes;
+my @func_include_regexes;
my @func_exclude_regexes;
my %test_names;
-my @src_regexes;
+my @src_include_regexes;
my @src_exclude_regexes;
my $verbose = 0;
@@ -30,7 +30,7 @@ my $skip_func = 0;
sub is_function_excluded($)
{
- return 0 if (!@func_regexes && !@func_exclude_regexes);
+ return 0 if (!@func_include_regexes && !@func_exclude_regexes);
my $func = shift;
@@ -38,28 +38,28 @@ sub is_function_excluded($)
return 1 if ($func =~ m/$r/);
}
- return 0 if (!@func_regexes);
+ return 0 if (!@func_include_regexes);
- foreach my $r (@func_regexes) {
+ foreach my $r (@func_include_regexes) {
return 0 if ($func =~ m/$r/);
}
return 1;
}
-sub filter_file($)
+sub is_file_excluded($)
{
my $s = shift;
- return 0 if (!@src_regexes && !@src_exclude_regexes);
+ return 0 if (!@src_include_regexes && !@src_exclude_regexes);
foreach my $r (@src_exclude_regexes) {
return 1 if ($s =~ m/$r/);
}
- return 0 if (!@src_regexes);
+ return 0 if (!@src_include_regexes);
- foreach my $r (@src_regexes) {
+ foreach my $r (@src_include_regexes) {
return 0 if ($s =~ m/$r/);
}
@@ -107,7 +107,7 @@ sub parse_info_data($)
$files{$source} = 1;
# Just ignore files explictly set as such
- $ignore = filter_file($source);
+ $ignore = is_file_excluded($source);
next;
}
@@ -189,7 +189,7 @@ sub parse_info_data($)
# Ignore DA/BRDA that aren't associated with functions
# Those are present on header files (maybe defines?)
- next if (@func_regexes && !$has_func);
+ next if (@func_include_regexes && !$has_func);
# FNF:<number of functions found>
if (m/^FNF:(-?\d+)/) {
@@ -899,10 +899,10 @@ GetOptions(
"only-i915|only_i915" => \$only_i915,
"only-drm|only_drm" => \$only_drm,
"func-filters|f=s" => \$func_filters,
- "include-func=s" => \@func_regexes,
+ "include-func=s" => \@func_include_regexes,
"exclude-func=s" => \@func_exclude_regexes,
"source-filters|S=s" => \$src_filters,
- "include-source=s" => \@src_regexes,
+ "include-source=s" => \@src_include_regexes,
"exclude-source=s" => \@src_exclude_regexes,
"show-files|show_files" => \$show_files,
"show-lines|show_lines" => \$show_lines,
@@ -935,9 +935,9 @@ my $str;
if ($only_i915) {
# Please keep in sync with the documentation
push @src_exclude_regexes, "selftest";
- push @src_regexes, "drm/i915";
- push @src_regexes, "drm/ttm";
- push @src_regexes, "drm/vgem";
+ push @src_include_regexes, "drm/i915";
+ push @src_include_regexes, "drm/ttm";
+ push @src_include_regexes, "drm/vgem";
}
if ($only_drm) {
@@ -946,21 +946,21 @@ if ($only_drm) {
push @src_exclude_regexes, "^/drm/";
}
-$str = open_filter_file($func_filters, \@func_regexes, \@func_exclude_regexes);
+$str = open_filter_file($func_filters, \@func_include_regexes, \@func_exclude_regexes);
if ($str) {
$filter_str .= "," if ($filter_str ne "");
$filter_str .= " function regex ($str)";
$has_filter = 1;
}
-$str = open_filter_file($src_filters, \@src_regexes, \@src_exclude_regexes);
+$str = open_filter_file($src_filters, \@src_include_regexes, \@src_exclude_regexes);
if ($str) {
$filter_str .= "," if ($filter_str ne "");
$filter_str .= " source regex ($str)";
$has_filter = 1;
}
-$ignore_unused = 1 if (@func_regexes || @func_exclude_regexes);
+$ignore_unused = 1 if (@func_include_regexes || @func_exclude_regexes);
if ($ignore_unused) {
$filter_str .= "," if ($filter_str ne "");
--
2.39.0
next prev parent reply other threads:[~2023-01-17 14:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 14:05 [igt-dev] [PATCH i-g-t 00/12] Improve code coverage tool Mauro Carvalho Chehab
2023-01-17 14:05 ` [igt-dev] [PATCH i-g-t 01/12] code_cov_parse_info: silent some messages by default Mauro Carvalho Chehab
2023-01-17 14:05 ` Mauro Carvalho Chehab [this message]
2023-01-17 14:05 ` [igt-dev] [PATCH i-g-t 03/12] code_cov_parse_info: use numberic sort for line numbers Mauro Carvalho Chehab
2023-01-17 14:05 ` [igt-dev] [PATCH i-g-t 04/12] code_cov_parse_info: better handle include regexes Mauro Carvalho Chehab
2023-01-17 14:06 ` [igt-dev] [PATCH i-g-t 05/12] code_cov_parse_info: add a tool to analyze branch coverage Mauro Carvalho Chehab
2023-01-17 14:06 ` [igt-dev] [PATCH i-g-t 06/12] code_cov_parse_info: add support for parsing JSON files Mauro Carvalho Chehab
2023-01-25 14:18 ` Kamil Konieczny
2023-01-17 14:06 ` [igt-dev] [PATCH i-g-t 07/12] code_cov_parse_info: add support for compressed files Mauro Carvalho Chehab
2023-01-17 14:06 ` [igt-dev] [PATCH i-g-t 08/12] code_cov_parse_info: allow specifying the source directory Mauro Carvalho Chehab
2023-01-17 14:06 ` [igt-dev] [PATCH i-g-t 09/12] code_cov_parse_info: better handle branch filtering Mauro Carvalho Chehab
2023-01-17 14:06 ` [igt-dev] [PATCH i-g-t 10/12] code_cov_parse_info: filter out branches from headers by default Mauro Carvalho Chehab
2023-01-17 14:06 ` [igt-dev] [PATCH i-g-t 11/12] code_cov_parse_info: add support for filtering branches Mauro Carvalho Chehab
2023-01-17 14:06 ` [igt-dev] [PATCH i-g-t 12/12] code_cov_parse_info: add support for filtering Xe driver data Mauro Carvalho Chehab
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=20230117140607.2759816-3-mauro.chehab@linux.intel.com \
--to=mauro.chehab@linux.intel.com \
--cc=igt-dev@lists.freedesktop.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