Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

THIS IS A TEST OF AUTOMATIC VERSION NUMBERING #15

Closed
Mightyjo opened this issue Mar 26, 2021 · 0 comments
Closed

THIS IS A TEST OF AUTOMATIC VERSION NUMBERING #15

Mightyjo opened this issue Mar 26, 2021 · 0 comments
Milestone
2.6.5-TEST

Comments

@Mightyjo
Copy link
Owner

THIS IS NOT VERSION 2.6.5
@Mightyjo Mightyjo added this to the 2.6.5-TEST milestone Mar 26, 2021
Mightyjo pushed a commit that referenced this issue Jun 3, 2021
@eric-s-raymond
Create m4 symbols for things that used to be generated as int literals.
90bf7c7 
Changes the generated C sources from the tests, but only by making
them easier to read.  In future patches this is going to make them
easier to compare by eyeball as well.

#15 in the retargeting patch series
Mightyjo pushed a commit that referenced this issue Jun 3, 2021
@eric-s-raymond
gen_backing_up() becomes an m4 macro.
6711981 
Generated-code changes consist of whitespace and a comment.

Thus patch also fixes the computation of two guard symbols
that weren't actually used yet, prospectively introduced in
patch #15 of this series. At the time I wrote that I didn't
understand what num_backing_up was doing and failed to
translate it properly.

#19 in the retargeting patch series
Mightyjo pushed a commit that referenced this issue Jun 3, 2021
@eric-s-raymond
gen_next_match() becomes m4 code.
3078880 
To verify this patch, notice that the non-whitespace changes in the
generated C from the tests are of only three kinds:

1. Addition of comments.  I elected to copy the comments from the
generator functions into their corresponding m4 macros in hopes of
making the generated code less nasty to read.

2. Lines like "if ( yy_current_state >= 12 )" changing so the numeric
literal is replaced by YY_JAMSTATE + 1. This was a consequence of the
change in #15 to simplify the C code generators so they could be
translated into static nacros.

3. "YY_CHAR yy_c = yy_ec[YY_SC_TO_UI(*yy_cp)]" being replaced by
"YY_CHAR yy_c = *(yy_ec+YY_SC_TO_UI(*yy_cp));".  The strange way of indexing yy_ec
avoids a syntactic collision with the use of [] as m4 quotes.

#20 in the retargeting patch series
Mightyjo pushed a commit that referenced this issue Jun 3, 2021
@eric-s-raymond
gen_next_state(true) becomes m4 code.
01f4aad 
As with patch #20 in this series, the changes in generated code fall in the classes:

1. Addition of comments.  I elected to copy the comments from the
   generator functions into their corresponding m4 macros in hopes of
   making the generated code less nasty to read.

2. Lines like "if ( yy_current_state >= 12 )" changing so the numeric
   literal is replaced by YY_JAMSTATE + 1. This was a consequence of the
   change in #15 to simplify the C code generators so they could be
   translated into static nacros.

3. "YY_CHAR yy_c = (*yy_cp ? yy_ec[YY_SC_TO_UI(*yy_cp)] : YY_NUL_EC);:
   being replaced by "YY_CHAR yy_c = (*yy_cp ?
   *(yy_ec+YY_SC_TO_UI(*yy_cp)) : YY_NUL_EC);" The strange way of
   indexing yy_ec avoids a syntactic collision with the use of [] as
   m4 quotes.

The gen_next_state(false) case was translated to m4 at patch #20

#22 in the retargeting patch series
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
2.6.5-TEST
Development

No branches or pull requests
1 participant
@Mightyjo