Displaying 7 results from an estimated 7 matches for "yy_current_buffer".
2012 Nov 29
2
[LLVMdev] problem trying to write an LLVM register-allocation pass
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
2012 Dec 01
0
[LLVMdev] problem trying to write an LLVM register-allocation pass
...0 );
skelout();
if ( ! C_plus_plus )
{
if ( use_read )
{
outn(
"\tif ( (result = read( fileno(yyin), (char *) buf, max_size )) < 0 ) \\" );
outn(
"\t\tYY_FATAL_ERROR( \"input in flex scanner failed\" );" );
}
else
{
outn(
"\tif ( yy_current_buffer->yy_is_interactive ) \\" );
outn( "\t\t{ \\" );
outn( "\t\tint c = '*', n; \\" );
outn( "\t\tfor ( n = 0; n < max_size && \\" );
outn( "\t\t\t (c = getc( yyin )) != EOF && c != '\\n'; ++n ) \\" );
ou...
2005 May 17
2
[LLVMdev] Scheme + LLVM JIT
...t'll be leaked now.
However, in 'Lexer.l', you have the following code:
<<EOF>> {
/* Make sure to free the internal buffers for flex when we are
* done reading our input!
*/
yy_delete_buffer(YY_CURRENT_BUFFER);
return EOF;
}
Which should take care of it.
> > I havn't tested parsing strings yet. My code is extremely simple and
> > *should* work, but we know where that line of thinking leads. Should I
> > submit a test case (it would have to be a C...
2011 Jun 02
48
[PATCH 0/9] libxl: disk configuration handling
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.
2005 May 17
0
[LLVMdev] Scheme + LLVM JIT
...ver, in 'Lexer.l', you have the following code:
>
>
> <<EOF>> {
> /* Make sure to free the internal buffers for flex when we are
> * done reading our input!
> */
> yy_delete_buffer(YY_CURRENT_BUFFER);
> return EOF;
> }
>
> Which should take care of it.
Ok, that makes sense.
> I made a 'FibInC' example that uses my little c-wrapper (which in turn
> uses this). I can submit all of those when they are cleaned up (and
> linking correc...
2005 May 16
0
[LLVMdev] Scheme + LLVM JIT
On Fri, 13 May 2005, Alexander Friedman wrote:
>>> This requires being able to parse strings. The LLVM 'Parser.h' interface
>>> (and implementation) has the built in assumptions that it will always be
>>> parsing from the file system. Would you guys accept a patch that makes
>>> it more general (ie, parse from file or string)?
>>
>> Yes,
2005 May 13
3
[LLVMdev] Scheme + LLVM JIT
> > This requires being able to parse strings. The LLVM 'Parser.h' interface
> > (and implementation) has the built in assumptions that it will always be
> > parsing from the file system. Would you guys accept a patch that makes
> > it more general (ie, parse from file or string)?
>
> Yes, that's a generally useful thing to have, I'd like to see it