From 561079c8601d7ded6fe958b4cec3d0f7aec1ee63 Mon Sep 17 00:00:00 2001 From: "Frank Ch. Eigler" Date: Thu, 8 Oct 2009 09:57:43 -0400 Subject: PR10702: preprocessor conditional for kernel CONFIG_foo * session.h (kernel_config[]): New session field. * main.cxx (parse_kernel_config): Populate it. * parse.cxx (eval_comparison): Use it. * testsuite/buildok/utrace.stp, testsuite/parseok/kconfig.stp: New tests. * NEWS, stap.1.in, doc/langref.tex: Mention it. --- stap.1.in | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) (limited to 'stap.1.in') diff --git a/stap.1.in b/stap.1.in index e6370dfc..b6f79fe9 100644 --- a/stap.1.in +++ b/stap.1.in @@ -340,12 +340,21 @@ by If, on the other hand, the first part is the identifier .BR arch to refer to the processor architecture (as named by the kernel -build system ARCH/SUBARCH), then the second part then the second +build system ARCH/SUBARCH), then the second part is one of the two string comparison operators .BR == " or " != , and the third part is a string literal for matching it. This comparison is a wildcard (mis)match. .PP +Similarly, if the first part is an identifier like +.BR CONFIG_something +to refer to a kernel configuration option, then the second part is +.BR == " or " != , +and the third part is a string literal for matching the value +(commonly "y" or "m"). Nonexistent or unset kernel configuration +options are represented by the empty string. This comparison is also +a wildcard (mis)match. +.PP Otherwise, the CONDITION is expected to be a comparison between two string literals or two numeric literals. In this case, the arguments are the only variables usable. -- cgit