search for: 1waknzu7

...*}}, //{{*}}-NEXT, //{{*}}-SAME and etc. >> 8. Prefix with regular expressions - If statement should be checked if prefix matches some regular expression, it should be used {{regex}}:, {{regex}}-NEXT and etc. >> >> More information in file https://docs.google.com/document/d/1wAKNzU7-S2EeK1-aADwgP8dEiKfByKNazonybCQW3zs/edit?usp=sharing. > > I noticed the google doc stated that multi-line patterns are not > supported. That's not actually the case, although it's a bit obscure: > the [[:space:]] character-class will match EOL and allow you to write > a multi...

...x, it should be used //{{*}}, //{{*}}-NEXT, //{{*}}-SAME and etc. 8. Prefix with regular expressions - If statement should be checked if prefix matches some regular expression, it should be used {{regex}}:, {{regex}}-NEXT and etc. More information in file https://docs.google.com/document/d/1wAKNzU7-S2EeK1-aADwgP8dEiKfByKNazonybCQW3zs/edit?usp=sharing. Now we have prototype with these features. It's tested on LLVM 3.8. There was found unsupported before directive in old test. Bug about this - https://llvm.org/bugs/show_bug.cgi?id=27852. There is about 6% slowdown with new features when w...

...be used //{{*}}, //{{*}}-NEXT, //{{*}}-SAME and etc. > 8.       Prefix with regular expressions - If statement should be checked if prefix matches some regular expression, it should be used {{regex}}:, {{regex}}-NEXT  and etc. > > More information in file https://docs.google.com/document/d/1wAKNzU7-S2EeK1-aADwgP8dEiKfByKNazonybCQW3zs/edit?usp=sharing. I noticed the google doc stated that multi-line patterns are not supported. That's not actually the case, although it's a bit obscure: the [[:space:]] character-class will match EOL and allow you to write a multi-line CHECK. > >...

...ould be checked if > prefix matches some regular expression, it should be used {{regex}}:, > {{regex}}-NEXT and etc. I'm not a fan of this ^ feature. I think it'll make testcases much harder to understand. > > More information in file > https://docs.google.com/document/d/1wAKNzU7-S2EeK1-aADwgP8dEiKfByKNazonybCQW3zs/edit?usp=sharing. > > Now we have prototype with these features. It’s tested on LLVM 3.8. > > There was found unsupported before directive in old test. Bug about > this > - https://llvm.org/bugs/show_bug.cgi?id=27852. > > There is about 6...

...hould be checked if > prefix matches some regular expression, it should be used {{regex}}:, > {{regex}}-NEXT and etc. I'm not a fan of this ^ feature. I think it'll make testcases much harder to understand. > > More information in file > https://docs.google.com/document/d/1wAKNzU7-S2EeK1-aADwgP8dEiKfByKNazonybCQW3zs/edit?usp=sharing. > > Now we have prototype with these features. It’s tested on LLVM 3.8. > > There was found unsupported before directive in old test. Bug about this > - https://llvm.org/bugs/show_bug.cgi?id=27852. > > There is about 6% slow...

...fix matches some regular expression, it should be used {{regex}}:, >> {{regex}}-NEXT and etc. > > I'm not a fan of this ^ feature. I think it'll make testcases much harder to understand. > >> >> More information in file >> https://docs.google.com/document/d/1wAKNzU7-S2EeK1-aADwgP8dEiKfByKNazonybCQW3zs/edit?usp=sharing. >> >> Now we have prototype with these features. It’s tested on LLVM 3.8. >> >> There was found unsupported before directive in old test. Bug about >> this >> - https://llvm.org/bugs/show_bug.cgi?id=27852. &gt...

...ix matches some regular expression, it should be used {{regex}}:, >> {{regex}}-NEXT and etc. > > I'm not a fan of this ^ feature. I think it'll make testcases much harder to understand. > >> >> More information in file >> https://docs.google.com/document/d/1wAKNzU7-S2EeK1-aADwgP8dEiKfByKNazonybCQW3zs/edit?usp=sharing. >> >> Now we have prototype with these features. It’s tested on LLVM 3.8. >> >> There was found unsupported before directive in old test. Bug about >> this >> - https://llvm.org/bugs/show_bug.cgi?id=27852. &g...

...be used //{{*}}, //{{*}}-NEXT, //{{*}}-SAME and etc. > 8.       Prefix with regular expressions - If statement should be checked if prefix matches some regular expression, it should be used {{regex}}:, {{regex}}-NEXT  and etc. > > More information in file https://docs.google.com/document/d/1wAKNzU7-S2EeK1-aADwgP8dEiKfByKNazonybCQW3zs/edit?usp=sharing. I noticed the google doc stated that multi-line patterns are not supported. That's not actually the case, although it's a bit obscure: the [[:space:]] character-class will match EOL and allow you to write a multi-line CHECK. > >...

...*}}-SAME > and etc. > > 8. Prefix with regular expressions - If statement should be checked > if prefix matches some regular expression, it should be used {{regex}}:, > {{regex}}-NEXT and etc. > > > > More information in file > https://docs.google.com/document/d/1wAKNzU7-S2EeK1-aADwgP8dEiKfByKNazonybCQW3zs/edit?usp=sharing > . > > > > Now we have prototype with these features. It’s tested on LLVM 3.8. > > There was found unsupported before directive in old test. Bug about this - > https://llvm.org/bugs/show_bug.cgi?id=27852. > > > &...

...be used //{{*}}, //{{*}}-NEXT, //{{*}}-SAME and etc. > 8.       Prefix with regular expressions - If statement should be checked if prefix matches some regular expression, it should be used {{regex}}:, {{regex}}-NEXT  and etc. > > More information in file https://docs.google.com/document/d/1wAKNzU7-S2EeK1-aADwgP8dEiKfByKNazonybCQW3zs/edit?usp=sharing. I noticed the google doc stated that multi-line patterns are not supported. That's not actually the case, although it's a bit obscure: the [[:space:]] character-class will match EOL and allow you to write a multi-line CHECK. > >...