Displaying 4 results from an estimated 4 matches for "notstr".
Did you mean:
netstr
2007 Nov 11
0
Patch to sshd match
...match
+ * -1 error
+ */
static int
-match_cfg_line_group(const char *grps, int line, const char *user)
+match_cfg_line_group(const char *grps, int line, const char *user, int not)
{
int result = 0;
u_int ngrps = 0;
char *arg, *p, *cp, *grplist[MAX_MATCH_GROUPS];
struct passwd *pw;
+ char* notstr = not ? "!" : "";
/*
* Even if we do not have a user yet, we still need to check for
@@ -529,12 +537,12 @@
} else if (ga_init(pw->pw_name, pw->pw_gid) == 0) {
debug("Can't Match group because user %.100s not in any group "
"at line %d&...
2012 Sep 07
1
[LLVMdev] teaching FileCheck to handle variations in order
...k;
}
// If this is a fixed string pattern, just match it now.
@@ -447,6 +468,9 @@ struct CheckString {
/// IsCheckNext - This is true if this is a CHECK-NEXT: directive (as opposed
/// to a CHECK: directive.
bool IsCheckNext;
+ int PushPos;
+ int PopPos;
+ SMLoc PopLoc;
/// NotStrings - These are all of the strings that are disallowed from
/// occurring between this match string and the previous one (or start of
@@ -454,7 +478,7 @@ struct CheckString {
std::vector<std::pair<SMLoc, Pattern> > NotStrings;
CheckString(const Pattern &P, SMLoc L, bool i...
2012 Sep 07
5
[LLVMdev] teaching FileCheck to handle variations in order
...k;
}
// If this is a fixed string pattern, just match it now.
@@ -447,6 +468,9 @@ struct CheckString {
/// IsCheckNext - This is true if this is a CHECK-NEXT: directive (as opposed
/// to a CHECK: directive.
bool IsCheckNext;
+ int PushPos;
+ int PopPos;
+ SMLoc PopLoc;
/// NotStrings - These are all of the strings that are disallowed from
/// occurring between this match string and the previous one (or start of
@@ -454,7 +478,7 @@ struct CheckString {
std::vector<std::pair<SMLoc, Pattern> > NotStrings;
CheckString(const Pattern &P, SMLoc L, bool i...
2012 Sep 07
0
[LLVMdev] teaching FileCheck to handle variations in order
On 9/7/2012 7:20 AM, Matthew Curtis wrote:
>
> The attached patch implements one possible solution. It introduces a
> position stack and a couple of directives:
>
> * 'CHECK-PUSH:' pushes the current match position onto the stack.
> * 'CHECK-POP:' pops the top value off of the stack and uses it to set
> the current match position.
>
> The above