Displaying 7 results from an estimated 7 matches for "readcheckfil".
Did you mean:
readcheckfile
2012 Sep 07
1
[LLVMdev] teaching FileCheck to handle variations in order
...tring(const Pattern &P, SMLoc L, bool isCheckNext)
- : Pat(P), Loc(L), IsCheckNext(isCheckNext) {}
+ : Pat(P), Loc(L), IsCheckNext(isCheckNext), PushPos(0), PopPos(0) {}
};
/// CanonicalizeInputFile - Remove duplicate horizontal space from the specified
@@ -517,6 +541,8 @@ static bool ReadCheckFile(SourceMgr &SM,
StringRef Buffer = F->getBuffer();
std::vector<std::pair<SMLoc, Pattern> > NotMatches;
+ int NextCheckPopPos= 0;
+ SMLoc NextCheckPopLoc;
while (1) {
// See if Prefix occurs in the memory buffer.
@@ -531,6 +557,7 @@ static bool ReadCheckFile(So...
2012 Sep 07
5
[LLVMdev] teaching FileCheck to handle variations in order
...tring(const Pattern &P, SMLoc L, bool isCheckNext)
- : Pat(P), Loc(L), IsCheckNext(isCheckNext) {}
+ : Pat(P), Loc(L), IsCheckNext(isCheckNext), PushPos(0), PopPos(0) {}
};
/// CanonicalizeInputFile - Remove duplicate horizontal space from the specified
@@ -517,6 +541,8 @@ static bool ReadCheckFile(SourceMgr &SM,
StringRef Buffer = F->getBuffer();
std::vector<std::pair<SMLoc, Pattern> > NotMatches;
+ int NextCheckPopPos= 0;
+ SMLoc NextCheckPopLoc;
while (1) {
// See if Prefix occurs in the memory buffer.
@@ -531,6 +557,7 @@ static bool ReadCheckFile(So...
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
2011 Jul 26
1
[LLVMdev] Correct use of StringRef and Twine
...eems like a step forward. While it is kinda gross, a subclass of StringRef is probably the lowest friction path to do this.
>
> Come to think of it - is there any use for StringRef other than as
> function arguments?
StringRef is useful for other things, for example the parsing logic in ReadCheckFile in utils/FileCheck.cpp uses it effectively. It really wants "reference into another string" that is efficient to .substr() etc.
> If we get Twine to be 'better' for function
> arguments than StringRef, then StringRef goes away - or put another
> way: StringRef could b...
2010 May 29
1
[LLVMdev] SVN version fails to compile
...(.text+0x16b5):
In function `CanonicalizeInputFile':
/tmp/llvm-svn/llvm/utils/FileCheck/FileCheck.cpp:464: undefined
reference to `llvm::MemoryBuffer::getMemBufferCopy(llvm::StringRef, char
const*)'
/tmp/llvm-svn/llvm-objects/utils/FileCheck/Debug/FileCheck.o(.text+0x1767):
In function `ReadCheckFile':
/tmp/llvm-svn/llvm/utils/FileCheck/FileCheck.cpp:478: undefined
reference to `llvm::MemoryBuffer::getFileOrSTDIN(llvm::StringRef,
std::basic_string<char, std::char_traits<char>, std::allocator<char> >*,
long long, stat*)'
/tmp/llvm-svn/llvm-objects/utils/FileCheck/De...
2011 Jul 25
0
[LLVMdev] Correct use of StringRef and Twine
> Right, but that requires VS #ifdefs. You can also use enum bitfields, but VS has different promotion rules from them than other compilers.
Ah, I'd thought that feature (specifying the backing type with "enum
name : integral_type") was standard, but I see it's a C++0x thing. My
mistake.
>> 1) the easy solution: create a StringRef subclass (or new type with a
>>
2011 Jul 24
2
[LLVMdev] Correct use of StringRef and Twine
On Jul 24, 2011, at 12:09 AM, David Blaikie wrote:
>> Yes, exactly. I'm just saying that I think the additional clarity of:
>> "foo" + Twine('x')
>>
>> is worth the inconvenience.
>
> Ok, attached a modified version of my patch with an Twine(char),
> Twine(unsigned char), and Twine(signed char). All three are explicit &
> have