search for: yyparse

.../llvm-gcc4.2-objects/gcc/../../llvm- gcc4.2-2.4.source/gcc/gengtype.c:3070: undefined reference to `_parse_file' /cygdrive/r/android/llvm/llvm-gcc4.2-objects/gcc/../../llvm- gcc4.2-2.4.source/gcc/gengtype.c:3070: undefined reference to `_parse_file' build/gengtype-yacc.o: In function `yyparse': /cygdrive/r/android/llvm/llvm-gcc4.2-objects/gcc/../../llvm- gcc4.2-2.4.source/gcc/gengtype-yacc.y:73: undefined reference to `_lexer_line' /cygdrive/r/android/llvm/llvm-gcc4.2-objects/gcc/../../llvm- gcc4.2-2.4.source/gcc/gengtype-yacc.y:75: undefined reference to `_lexer_line'...

.../../../llvm- > gcc4.2-2.4.source/gcc/gengtype.c:3070: undefined reference to > `_parse_file' > /cygdrive/r/android/llvm/llvm-gcc4.2-objects/gcc/../../llvm- > gcc4.2-2.4.source/gcc/gengtype.c:3070: undefined reference to > `_parse_file' > build/gengtype-yacc.o: In function `yyparse': > /cygdrive/r/android/llvm/llvm-gcc4.2-objects/gcc/../../llvm- > gcc4.2-2.4.source/gcc/gengtype-yacc.y:73: undefined reference to > `_lexer_line' > /cygdrive/r/android/llvm/llvm-gcc4.2-objects/gcc/../../llvm- > gcc4.2-2.4.source/gcc/gengtype-yacc.y:75: undefined reference t...

...ed-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -c expr.c cc1: warnings being treated as errors /src/bin/expr/expr.y: In function 'main': /src/bin/expr/expr.y:291: warning: implicit declaration of function 'yyparse' /src/bin/expr/expr.y:291: warning: nested extern declaration of 'yyparse' expr.c: At top level: expr.c:813: warning: no previous prototype for 'yyparse' *** Error code 1 Stop in /src/bin/expr. *** Error code 1 Stop in /src/bin. *** Error code 1 Stop in /src. *** Error code 1...

No idea why this happens: index-parse.y: In function 'yyparse': index-parse.c:1256:6: error: assuming pointer wraparound does not occur when comparing P +- C1 with P +- C2 [-Werror=strict-overflow] if (yyss + yystacksize - 1 <= yyssp) ^ It only happens on one machine, and not on any others, even though they have similar versions of gcc and bi...

...function bar. > > Neither register RBP nor register EBP is saved/restored across the call > from foo to bar, either by the code for the call or the code for entry to > bar. > > The input C file that is causing this problem is flex.c (attached). The > calling function is "yyparse" and the called function is "scinstal". > > Here are the reserved registers for yyparse: { 7 44 54 106 111 114 118 } > > Here are the reserved registers for scinstal: { 54 111 114 } > > Register EBP is preg 44, which is NOT in the reserved list for scinstal > (no...

...) { fprintf (stderr, "syntax error at line %d: %s\n", - yylloc.first_line, msg); + yylloc->first_line, msg); +} + +int +do_parse (struct parse_context *context, FILE *in) +{ + yyscan_t scanner; + int res; + + scanner_init (&scanner, context, in); + res = yyparse (scanner, context); + scanner_destroy (scanner); + + return res; } diff --git a/builder/index-parser-c.c b/builder/index-parser-c.c index fbbebff..7aeb6d0 100644 --- a/builder/index-parser-c.c +++ b/builder/index-parser-c.c @@ -43,7 +43,7 @@ extern void unix_error (int errcode, char * cmdname, v...

...> Neither register RBP nor register EBP is saved/restored across the > call from foo to bar, either by the code for the call or the code > for entry to bar. > > The input C file that is causing this problem is flex.c > (attached). The calling function is "yyparse" and the called > function is "scinstal". > > Here are the reserved registers for yyparse: { 7 44 54 106 111 114 > 118 } > > Here are the reserved registers for scinstal: { 54 111 114 } > > Register EBP is preg 44, which is NOT in the reser...

.../llvm- > gcc4.2-2.4.source/gcc/gengtype.c:3070: undefined reference to > `_parse_file' > /cygdrive/r/android/llvm/llvm-gcc4.2-objects/gcc/../../llvm- > gcc4.2-2.4.source/gcc/gengtype.c:3070: undefined reference to > `_parse_file' > build/gengtype-yacc.o: In function `yyparse': > /cygdrive/r/android/llvm/llvm-gcc4.2-objects/gcc/../../llvm- > gcc4.2-2.4.source/gcc/gengtype-yacc.y:73: undefined reference to > `_lexer_line' > /cygdrive/r/android/llvm/llvm-gcc4.2-objects/gcc/../../llvm- > gcc4.2-2.4.source/gcc/gengtype-yacc.y:75: undefined referen...

...-Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -c expr.c cc1: warnings being treated as errors expr.c:812: warning: redundant redeclaration of 'yyparse' /usr/src/bin/expr/expr.y:77: warning: previous declaration of 'yyparse' was here *** [expr.o] Error code 1 Stop in /usr/src/bin/expr. *** [all] Error code 1 Stop in /usr/src/bin. *** [bin.all__D] Error code 1 Stop in /usr/src. *** [everything] Error code 1 Stop in /usr/src. *** [b...

...arser be made to accept as valid what is otherwise possible when using `[[<` ? Best, Laurent Le sam. 30 nov. 2019 ? 17:33, Laurent Gautier <lgautier at gmail.com> a ?crit : > I found the following code comment in `src/main/gram.c`: > > ``` > > /* Memory leak > > yyparse(), as generated by bison, allocates extra space for the parser > stack using malloc(). Unfortunately this means that there is a memory > leak in case of an R error (long-jump). In principle, we could define > yyoverflow() to relocate the parser stacks for bison and allocate say on > the...

Hi, The behavior of ``` SEXP R_ParseVector(SEXP, int, ParseStatus *, SEXP); ``` defined in `src/include/R_ext/Parse.h` appears to be inconsistent depending on the string to be parsed. Trying to parse a string such as `"list(''=1+"` sets the `ParseStatus` to incomplete parsing error but trying to parse `"list(''=123"` will result in R sending a message to the

...r e.g. below. // common code from the two 'RunVMAsmParser' functions static Module* RunParser(Module * M) { llvmAsmlineno = 1; // Reset the current line number... CurModule.CurrentModule = M; #if YYDEBUG yydebug = Debug; #endif // Check to make sure the parser succeeded if (yyparse()) { if (ParserResult) delete ParserResult; return 0; } Cheers, George Russell -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20071111/f4a660e0/attachment.html>

Hi Susan, RBP is used as the frame pointer on x86 (hence its automatic appearance in your code), and shouldn't be allocated to any vreg in function bar. Loading/saving RBP should be managed by the stack frame setup/teardown code. If it doesn't already, your allocator should filter out reserved registers (See MachineRegisterInfo::isReserved(unsigned preg)) when assigning physregs.

...33 fffffd7fff31c681 dt_cook_op3 () + 31 fffffd7fff31d61b dt_node_cook () + 33 fffffd7fff31cda7 dt_cook_member () + 17 fffffd7fff31d61b dt_node_cook () + 33 fffffd7fff31ce8d dt_cook_xlator () + bd fffffd7fff31d61b dt_node_cook () + 33 fffffd7fff31924d dt_node_xlator () + 1c5 fffffd7fff2eb09b yyparse () + 6a3 fffffd7fff2f7ea4 dt_compile () + 294 fffffd7fff2f83cf dtrace_program_fcompile () + 27 fffffd7fff2f7a9a dt_load_libs_dir () + 11a fffffd7fff2f7bde dt_load_libs () + 3e fffffd7fff2f7c83 dt_compile () + 73 fffffd7fff2f839e dtrace_program_strcompile () + 26 0000000000404a80 compile_str...

...ent of a parse_context. */ diff --git a/builder/ini_reader.ml b/builder/ini_reader.ml index 68e3863..c64125c 100644 --- a/builder/ini_reader.ml +++ b/builder/ini_reader.ml @@ -27,10 +27,10 @@ and c_section = string * c_fields (* [name] + fields *) and c_fields = field array (* Calls yyparse in the C code. *) -external parse_index : prog:string -> string -> c_sections = "virt_builder_parse_index" +external parse_index : prog:string -> error_suffix:string -> string -> c_sections = "virt_builder_parse_index" -let read_ini ~prog file = - let sections...

...> > > > > Le sam. 30 nov. 2019 ? 17:33, Laurent Gautier <lgautier at gmail.com> a > ?crit : > > > >> I found the following code comment in `src/main/gram.c`: > >> > >> ``` > >> > >> /* Memory leak > >> > >> yyparse(), as generated by bison, allocates extra space for the parser > >> stack using malloc(). Unfortunately this means that there is a memory > >> leak in case of an R error (long-jump). In principle, we could define > >> yyoverflow() to relocate the parser stacks for bison a...

Hi, this series introduces a basic support for registering/attaching/unregistering RHEL guests using subscription-manager, so it is possible to do for example: $ cat <<EOF > sm.conf [general] username=user password=pass [attach-0] pool=ID EOF $ virt-customize -a rhel-guest.qcow2 \ --sm-config sm.conf --sm-register --sm-attach 0 \ --install pkg1 --install pkg2

I found the following code comment in `src/main/gram.c`: ``` /* Memory leak yyparse(), as generated by bison, allocates extra space for the parser stack using malloc(). Unfortunately this means that there is a memory leak in case of an R error (long-jump). In principle, we could define yyoverflow() to relocate the parser stacks for bison and allocate say on the R heap, but yyoverf...

On Mon, Dec 15, 2014 at 05:54:51PM +0000, Richard W.M. Jones wrote: > No idea why this happens: > > index-parse.y: In function 'yyparse': > index-parse.c:1256:6: error: assuming pointer wraparound does not occur when comparing P +- C1 with P +- C2 [-Werror=strict-overflow] > if (yyss + yystacksize - 1 <= yyssp) > ^ > > It only happens on one machine, and not on any others, even > though they have...

...version that I tried that doesn't work is 1.875. There's a couple bison releases in between those two that may or may not work, I haven't tried them. This isn't really an LLVM problem but it affects LLVM. The problem is that bison 1.875 inserts an __attribute__((unused)) into the yyparse function after a label. The #define this is wrapped in thinks its legal anytime after release 2.0.93. With GCC 3.3.2, it gives a compiler error that looks like: > Compiling llvmAsmParser.cpp > llvmAsmParser.tab.c: In function `int llvmAsmparse()': > llvmAsmParser.tab.c:4152: error: pa...