search for: yy_get_next_buffer

...er.l llvm[2]: Compiling FileLexer.cpp for Release build /home/rogelio/Desktop/llvm/utils/TableGen/FileLexer.l: In function 'int Filelex()': /home/rogelio/Desktop/llvm/utils/TableGen/FileLexer.l:205: error: 'STRCONCATTOK' was not declared in this scope Lexer.cpp: In function 'int yy_get_next_buffer()': Lexer.cpp:1369: warning: comparison between signed and unsigned integer expressions make[2]: *** [/home/rogelio/Desktop/llvm/utils/TableGen/Release/FileLexer.o] Error 1 make[2]: Leaving directory `/home/rogelio/Desktop/llvm/utils/TableGen' make[1]: *** [all] Error 1 make[1]: Leaving dir...

...rser/Lexer.l: In function 'int llvmAsmlex()': /home/borist/builds/llvm/lib/AsmParser/Lexer.l:278: error: 'PURE' was not declared in this scope /home/borist/builds/llvm/lib/AsmParser/Lexer.l:279: error: 'CONST' was not declared in this scope Lexer.cpp: In function 'int yy_get_next_buffer()': Lexer.cpp:2543: warning: comparison between signed and unsigned integer expressions make[2]: *** [/home/borist/builds/llvm/lib/AsmParser/Release/Lexer.o] Error 1 make[2]: Leaving directory `/home/borist/builds/llvm/lib/AsmParser' make[1]: *** [AsmParser/.makeall] Error 2 make[1]: Leav...

...lvm/lib/AsmParser/Lexer.l: In function 'int llvmAsmlex()': /usr/src/Lang/llvm/lib/AsmParser/Lexer.l:278: error: 'PURE' was not declared in this scope /usr/src/Lang/llvm/lib/AsmParser/Lexer.l:279: error: 'CONST' was not declared in this scope Lexer.cpp: In function 'int yy_get_next_buffer()': I'm on Debian/Sid/AMD64, build directory is /usr/src/Lang/llvm/_Obj (a subdir of the source). Even by removing /usr/src/Lang/llvm/lib/AsmParser/Lexer.cpp as suggested inhttp://lists.cs.uiuc.edu/pipermail/cfe-dev/2007-November/000483.html I'm getting the same message. I'm...

...ileLexer.cpp for Release build > /home/rogelio/Desktop/llvm/utils/TableGen/FileLexer.l: In function > 'int Filelex()': > /home/rogelio/Desktop/llvm/utils/TableGen/FileLexer.l:205: error: > 'STRCONCATTOK' was not declared in this scope > Lexer.cpp: In function 'int yy_get_next_buffer()': > Lexer.cpp:1369: warning: comparison between signed and unsigned > integer expressions > make[2]: *** [/home/rogelio/Desktop/llvm/utils/TableGen/Release/FileLexer.o] > Error 1 > make[2]: Leaving directory `/home/rogelio/Desktop/llvm/utils/TableGen' > make[1]: *** [all...

I've put the pre-release tar balls here: http://llvm.org/prereleases/1.7/ I'm asking for help to test this release and to review documentation. If anyone can spare some time to help out, I would really appreciate it. The more people that test, the better this release will be. Secondly, now that the tarballs have been created, everyone is free to check in documentation changes into the

...appears in.) > /usr/home/llvm/obj/../tools/llvmc/ConfigLexer.l: In function ` > llvm::ConfigLexerTokens llvm::Configlex()': > /usr/home/llvm/obj/../tools/llvmc/ConfigLexer.l:174: error: `assert' undeclared > (first use this function) > ConfigLexer.cpp: In function `int yy_get_next_buffer()': > ConfigLexer.cpp:1314: error: `assert' undeclared (first use this function) > ConfigLexer.cpp: In function `void yyunput(int, char*)': > ConfigLexer.cpp:1533: error: `assert' undeclared (first use this function) > ConfigLexer.cpp: In function `yy_buffer_state* Confi...

Reid, >As for Interix support in general, I'm having a hard time determining >which variant of Unix Interix implements. It seems to be partially Posix >1 and partially Posix 2 based. Do you have any further information >related to the specific standards supported by Interix? I don't want to >incorrectly categorize the Interix support. I've discussed this subject with

Jeff/Vladimir: As with Interix, I've recently added support for FreeBSD into lib/System. Currently, the implementation of FreeBSD just uses the "generic Unix" implementation which probably should work on FreeBSD. If not, I would appreciate it if you could make patches in the FreeBSD directory. If you do, don't forget that you need to remove anything that doesn't work in the

I have a new problem: Register RBP is used in a function foo. (I am not allocating RBP to any virtual register, the instances of RBP in function foo are in the machine code when my register allocator starts.) Function foo calls function bar. Register RBP is not saved across the call, though it is live after the call. Function bar includes a virtual register. The code that I'm using to

I think I posted this patch before, but it looks like it was in December 2012 (!). 1/1 libxl: introduce an option for disabling the non-O_DIRECT workaround Ideally it would go into 4.4, at least. Provided the corresponding qemu part has gone into qemu-xen, which I think it has. Can anyone confirm ?

...;, "%*", "#endif", "", "%- Standard (non-C++) definition", "static yy_state_type yy_get_previous_state YY_PROTO(( void ));", "static yy_state_type yy_try_NUL_trans YY_PROTO(( yy_state_type current_state ));", "static int yy_get_next_buffer YY_PROTO(( void ));", "static void yy_fatal_error YY_PROTO(( const char msg[] ));", "%*", "", "/* Done after the current pattern has been matched and before the", " * corresponding action - sets up yytext.", " */", &quot...

This is v3 of my disk series. What were previously patches 01-06 have been applied. These are the tested and updated remainder, addressing the previous comments. 1 Preparatory work. 2-4 The new parser and its documentation. 5-6 Replace old parsers with calls to the new one. 7-8 Two features, one of them essential. 9 Basic test suite for disk string parsing, as adhoc script.