search for: yyvsp

...bxlu_cfg_y.c" +#line 1141 "libxlu_cfg_y.c" break; default: @@ -1459,80 +1465,80 @@ yyreduce: YY_REDUCE_PRINT (yyn); switch (yyn) { - case 4: + case 9: /* Line 1455 of yacc.c */ -#line 51 "libxlu_cfg_y.y" - { xlu__cfg_set_store(ctx,(yyvsp[(1) - (4)].string),(yyvsp[(3) - (4)].setting),(yylsp[(3) - (4)]).first_line); ;} +#line 57 "libxlu_cfg_y.y" + { xlu__cfg_set_store(ctx,(yyvsp[(1) - (3)].string),(yyvsp[(3) - (3)].setting),(yylsp[(3) - (3)]).first_line); ;} break; - case 9: + case 12: /* Line 1455 of yacc.c...

# xl cpupool-create ''name="pool2" sched="credit2"'' command line:2: config parsing error near `sched'': syntax error, unexpected IDENT, expecting NEWLINE or '';'' Failed to parse config file: Invalid argument *** glibc detected *** xl: free(): invalid pointer: 0x0000000001a79a10 *** Segmentation fault (core dumped) Looking at the code

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

...2, 46, 1, 39, 40, 8, 5, 6, 7, 5, 6, 7, 11, 33, 33, 11, 35, 31, 36, 37, 28, 8, 4, 47, 3, 30, 0, 0, 29, 22, 57, 44, 66, 62 }; int yychar; int yylval; int yynerrs; int yyparse (void); int yyparse() { register int yystate; register int yyn; register short *yyssp; register int *yyvsp; int yyerrstatus; int yychar1 = 0; short yyssa[200]; int yyvsa[200]; short *yyss = yyssa; int *yyvs = yyvsa; int yystacksize = 200; int yyfree_stacks = 0; int yyval; int yylen; yystate = 0; yyerrstatus = 0; yynerrs = 0; yychar = -2; yyssp = yyss - 1; yyvsp = yyvs; yy...

...ts YYVAL to garbage. 1311 This behavior is undocumented and Bison 1312 users should not rely upon it. Assigning to YYVAL 1313 unconditionally makes the parser a bit smaller, and it avoids a 1314 GCC warning that YYVAL may be used uninitialized. */ 1315 yyval = yyvsp[1-yylen]; => 0x0000000000400c2d <rpcalc_parse+653>: movsd xmm0,QWORD PTR [rbx+rax*8] 0x0000000000400c32 <rpcalc_parse+658>: movsd QWORD PTR [rbp-0x808],xmm0 As far as I understand it, assigning to eax zero-extends to rax. However, eax holds the result of "1-yy...

...1311         This behavior is undocumented and Bison > 1312         users should not rely upon it.  Assigning to YYVAL > 1313         unconditionally makes the parser a bit smaller, and it avoids a > 1314         GCC warning that YYVAL may be used uninitialized.  */ > 1315      yyval = yyvsp[1-yylen]; > => 0x0000000000400c2d <rpcalc_parse+653>:       movsd  xmm0,QWORD PTR > [rbx+rax*8] >   0x0000000000400c32 <rpcalc_parse+658>:       movsd  QWORD PTR > [rbp-0x808],xmm0 > > > As far as I understand it, assigning to eax zero-extends to rax. > Howeve...

...: `yystate' might be used uninitialized in this function /usr/share/bison++/bison.cc:560: warning: `yyn' might be used uninitialized in this function /usr/share/bison++/bison.cc:561: warning: `yyssp' might be used uninitialized in this function /usr/share/bison++/bison.cc:562: warning: `yyvsp' might be used uninitialized in this function /usr/share/bison++/bison.cc:563: warning: `yyerrstatus' might be used uninitialized in this function flex -olex.yy.c ./ppl.l gcc -c -I. -I. -I../../include -I../../include -Wall -pipe - -fno-strict-aliasing -gstabs+ -Wpointer-arith -g -O2 -...

...yystate' might be used uninitialized in this function /usr/share/bison++/bison.cc:560: warning: `yyn' might be used uninitialized in this function /usr/share/bison++/bison.cc:561: warning: `yyssp' might be used uninitialized in this function /usr/share/bison++/bison.cc:562: warning: `yyvsp' might be used uninitialized in this function /usr/share/bison++/bison.cc:563: warning: `yyerrstatus' might be used uninitialized in this function gcc -c -I. -I. -I../../include -I../../include -Wall -pipe -fno-strict-aliasing -gstabs+ -Wpointer-arith -g -O2 -o lex.yy.o lex.yy.c ./p...