linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Namhyung Kim <namhyung@kernel.org>,
	linux-kernel@vger.kernel.org, Andi Kleen <ak@linux.intel.com>,
	Jin Yao <yao.jin@linux.intel.com>,
	John Garry <john.garry@huawei.com>, Paul Clarke <pc@us.ibm.com>,
	kajoljain <kjain@linux.ibm.com>,
	linux-perf-users@vger.kernel.org,
	Stephane Eranian <eranian@google.com>,
	Sandeep Dasgupta <sdasgup@google.com>
Subject: Re: [PATCH v8 3/8] perf expr: Modify code layout
Date: Wed, 22 Sep 2021 22:58:47 +0200	[thread overview]
Message-ID: <YUuZBwiW/0M7yosQ@krava> (raw)
In-Reply-To: <20210918063513.2356923-4-irogers@google.com>

On Fri, Sep 17, 2021 at 11:35:08PM -0700, Ian Rogers wrote:
> No functional change. Alter whitespace. Use helper macros that will be
> made more complex in a later change.

please split into more patches, with the spacing changes
it's not easy to check there's no functional change

thanks,
jirka

> 
> Signed-off-by: Ian Rogers <irogers@google.com>
> ---
>  tools/perf/util/expr.y | 149 +++++++++++++++++++++++------------------
>  1 file changed, 85 insertions(+), 64 deletions(-)
> 
> diff --git a/tools/perf/util/expr.y b/tools/perf/util/expr.y
> index 41c9cd4efadd..51f4f0aa1955 100644
> --- a/tools/perf/util/expr.y
> +++ b/tools/perf/util/expr.y
> @@ -2,23 +2,10 @@
>  %{
>  #define YYDEBUG 1
>  #include <math.h>
> -#include <stdio.h>
> -#include "util.h"
>  #include "util/debug.h"
> -#include <stdlib.h> // strtod()
> +#include "smt.h"
>  #define IN_EXPR_Y 1
>  #include "expr.h"
> -#include "smt.h"
> -#include <string.h>
> -
> -static double d_ratio(double val0, double val1)
> -{
> -	if (val1 == 0) {
> -		return 0;
> -	}
> -	return  val0 / val1;
> -}
> -
>  %}
>  
>  %define api.pure full
> @@ -33,11 +20,7 @@ static double d_ratio(double val0, double val1)
>  	char	*str;
>  }
>  
> -%token EXPR_PARSE EXPR_OTHER EXPR_ERROR
> -%token <num> NUMBER
> -%token <str> ID
> -%destructor { free ($$); } <str>
> -%token MIN MAX IF ELSE SMT_ON D_RATIO
> +%token ID NUMBER MIN MAX IF ELSE SMT_ON D_RATIO EXPR_ERROR EXPR_PARSE EXPR_OTHER
>  %left MIN MAX IF
>  %left '|'
>  %left '^'
> @@ -46,6 +29,9 @@ static double d_ratio(double val0, double val1)
>  %left '-' '+'
>  %left '*' '/' '%'
>  %left NEG NOT
> +%type <num> NUMBER
> +%type <str> ID
> +%destructor { free ($$); } <str>
>  %type <num> expr if_expr
>  
>  %{
> @@ -57,6 +43,12 @@ static void expr_error(double *final_val __maybe_unused,
>  	pr_debug("%s\n", s);
>  }
>  
> +#define BINARY_LONG_OP(RESULT, OP, LHS, RHS)				\
> +	RESULT = (long)LHS OP (long)RHS;
> +
> +#define BINARY_OP(RESULT, OP, LHS, RHS)					\
> +	RESULT = LHS OP RHS;
> +
>  %}
>  %%
>  
> @@ -78,49 +70,78 @@ MIN | MAX | IF | ELSE | SMT_ON | NUMBER | '|' | '^' | '&' | '-' | '+' | '*' | '/
>  '<' | '>' | D_RATIO
>  
>  all_expr: if_expr			{ *final_val = $1; }
> -	;
> -
> -if_expr:
> -	expr IF expr ELSE expr { $$ = $3 ? $1 : $5; }
> -	| expr
> -	;
> -
> -expr:	  NUMBER
> -	| ID			{
> -					struct expr_id_data *data;
> -
> -					$$ = NAN;
> -					if (expr__resolve_id(ctx, $1, &data) == 0)
> -						$$ = expr_id_data__value(data);
> -
> -					free($1);
> -				}
> -	| expr '|' expr		{ $$ = (long)$1 | (long)$3; }
> -	| expr '&' expr		{ $$ = (long)$1 & (long)$3; }
> -	| expr '^' expr		{ $$ = (long)$1 ^ (long)$3; }
> -	| expr '<' expr		{ $$ = $1 < $3; }
> -	| expr '>' expr		{ $$ = $1 > $3; }
> -	| expr '+' expr		{ $$ = $1 + $3; }
> -	| expr '-' expr		{ $$ = $1 - $3; }
> -	| expr '*' expr		{ $$ = $1 * $3; }
> -	| expr '/' expr		{ if ($3 == 0) {
> -					pr_debug("division by zero\n");
> -					YYABORT;
> -				  }
> -				  $$ = $1 / $3;
> -	                        }
> -	| expr '%' expr		{ if ((long)$3 == 0) {
> -					pr_debug("division by zero\n");
> -					YYABORT;
> -				  }
> -				  $$ = (long)$1 % (long)$3;
> -	                        }
> -	| '-' expr %prec NEG	{ $$ = -$2; }
> -	| '(' if_expr ')'	{ $$ = $2; }
> -	| MIN '(' expr ',' expr ')' { $$ = $3 < $5 ? $3 : $5; }
> -	| MAX '(' expr ',' expr ')' { $$ = $3 > $5 ? $3 : $5; }
> -	| SMT_ON		 { $$ = smt_on() > 0; }
> -	| D_RATIO '(' expr ',' expr ')' { $$ = d_ratio($3,$5); }
> -	;
>  
> -%%
> +if_expr: expr IF expr ELSE expr
> +{
> +	$$ = $3 ? $1 : $5;
> +}
> +| expr
> +;
> +
> +expr: NUMBER
> +{
> +	$$ = $1;
> +}
> +| ID
> +{
> +	struct expr_id_data *data;
> +
> +	$$ = NAN;
> +	if (expr__resolve_id(ctx, $1, &data) == 0)
> +		$$ = expr_id_data__value(data);
> +
> +	free($1);
> +}
> +| expr '|' expr { BINARY_LONG_OP($$, |, $1, $3); }
> +| expr '&' expr { BINARY_LONG_OP($$, &, $1, $3); }
> +| expr '^' expr { BINARY_LONG_OP($$, ^, $1, $3); }
> +| expr '<' expr { BINARY_OP($$, <, $1, $3); }
> +| expr '>' expr { BINARY_OP($$, >, $1, $3); }
> +| expr '+' expr { BINARY_OP($$, +, $1, $3); }
> +| expr '-' expr { BINARY_OP($$, -, $1, $3); }
> +| expr '*' expr { BINARY_OP($$, *, $1, $3); }
> +| expr '/' expr
> +{
> +	if ($3 == 0) {
> +		pr_debug("division by zero\n");
> +		YYABORT;
> +	}
> +	$$ = $1 / $3;
> +}
> +| expr '%' expr
> +{
> +	if ((long)$3 == 0) {
> +		pr_debug("division by zero\n");
> +		YYABORT;
> +	}
> +	$$ = (long)$1 % (long)$3;
> +}
> +| D_RATIO '(' expr ',' expr ')'
> +{
> +	if ($5 == 0) {
> +		$$ = 0;
> +	} else {
> +		$$ = $3 / $5;
> +	}
> +}
> +| '-' expr %prec NEG
> +{
> +	$$ = -$2;
> +}
> +| '(' if_expr ')'
> +{
> +	$$ = $2;
> +}
> +| MIN '(' expr ',' expr ')'
> +{
> +	$$ = $3 < $5 ? $3 : $5;
> +}
> +| MAX '(' expr ',' expr ')'
> +{
> +	$$ = $3 > $5 ? $3 : $5;
> +}
> +| SMT_ON
> +{
> +	$$ = smt_on() > 0 ? 1.0 : 0.0;
> +}
> +;
> -- 
> 2.33.0.464.g1972c5931b-goog
> 


  reply	other threads:[~2021-09-22 20:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-18  6:35 [PATCH v8 0/8] Don't compute events that won't be used in a metric Ian Rogers
2021-09-18  6:35 ` [PATCH v8 1/8] perf metric: Restructure struct expr_parse_ctx Ian Rogers
2021-09-22 20:59   ` Jiri Olsa
2021-09-23  0:21     ` Ian Rogers
2021-09-18  6:35 ` [PATCH v8 2/8] perf metric: Use NAN for missing event IDs Ian Rogers
2021-09-18  6:35 ` [PATCH v8 3/8] perf expr: Modify code layout Ian Rogers
2021-09-22 20:58   ` Jiri Olsa [this message]
2021-09-18  6:35 ` [PATCH v8 4/8] perf metric: Rename expr__find_other Ian Rogers
2021-09-18  6:35 ` [PATCH v8 5/8] perf metric: Add utilities to work on ids map Ian Rogers
2021-09-22 20:58   ` Jiri Olsa
2021-09-22 20:59   ` Jiri Olsa
2021-09-18  6:35 ` [PATCH v8 6/8] perf metric: Allow metrics with no events Ian Rogers
2021-09-18  6:35 ` [PATCH v8 7/8] perf metric: Don't compute unused events Ian Rogers
2021-09-18  6:35 ` [PATCH v8 8/8] perf test: Add metric test for eliminating events Ian Rogers
2021-09-20 13:46 ` [PATCH v8 0/8] Don't compute events that won't be used in a metric Andi Kleen

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=YUuZBwiW/0M7yosQ@krava \
    --to=jolsa@redhat.com \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=eranian@google.com \
    --cc=irogers@google.com \
    --cc=john.garry@huawei.com \
    --cc=kjain@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=pc@us.ibm.com \
    --cc=peterz@infradead.org \
    --cc=sdasgup@google.com \
    --cc=yao.jin@linux.intel.com \
    /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 NNTP newsgroup(s).