Searched refs:flex (Results 1 – 8 of 8) sorted by relevance
82 perf-util-y += parse-events-flex.o86 perf-util-y += pmu-flex.o158 perf-util-y += expr-flex.o274 $(Q)$(call echo-cmd,flex)$(FLEX) -o $(OUTPUT)util/parse-events-flex.c \282 $(OUTPUT)util/expr-flex.c $(OUTPUT)util/expr-flex.h: util/expr.l $(OUTPUT)util/expr-bison.c284 $(Q)$(call echo-cmd,flex)$(FLEX) -o $(OUTPUT)util/expr-flex.c \292 $(OUTPUT)util/pmu-flex.c $(OUTPUT)util/pmu-flex.h: util/pmu.l $(OUTPUT)util/pmu-bison.c294 $(Q)$(call echo-cmd,flex)$(FLEX) -o $(OUTPUT)util/pmu-flex.c \304 $(Q)$(call echo-cmd,flex)$(FLEX) -o $(OUTPUT)util/bpf-filter-flex.c \360 CFLAGS_pmu-flex.o += $(flex_flags)[all …]
114 $(OUTPUT)%-flex.o: $(OUTPUT)%-flex.c FORCE
31 *-flex.*
215 FLEX ?= flex910 $(OUTPUT)%-flex.o: %.c prepare FORCE1287 $(OUTPUT)FEATURE-DUMP $(OUTPUT)util/*-bison* $(OUTPUT)util/*-flex* \
186 # was to check the flex version to see if we can use compiler warnings as187 # errors for one of the cases flex generates code C compilers complains about.196 # check the flex version to see if we can use compiler warnings as errors for197 # one of the cases flex generates code C compilers complains about.
367 bool flex; in bpf_core_parse_spec() local373 flex = is_flex_arr(btf, acc - 1, a); in bpf_core_parse_spec()374 if (!flex && access_idx >= a->nelems) in bpf_core_parse_spec()643 bool flex; in bpf_core_spec_match() local649 flex = is_flex_arr(targ_btf, targ_acc - 1, a); in bpf_core_spec_match()650 if (!flex && local_acc->idx >= a->nelems) in bpf_core_spec_match()
6 LEX = flex
129 It's possible to include special rule if needed (like we do for flex or bison
Completed in 26 milliseconds