diff options
author | Akim Demaille <akim.demaille@gmail.com> | 2020-05-15 08:13:44 +0200 |
---|---|---|
committer | Akim Demaille <akim.demaille@gmail.com> | 2020-05-17 08:28:12 +0200 |
commit | 465babb635e551620f2f349496912d90c6738600 (patch) | |
tree | f2634ab3caed9f67007083a3f21d3c2b86f3ec18 /NEWS | |
parent | 6a28e6d412c0b8da5a5ee9540942366823301c6c (diff) | |
download | bison-465babb635e551620f2f349496912d90c6738600.tar.gz |
fix: do not emit nested comments
With input such as
%token<fl> yVL_CLOCK "/*verilator sc_clock*/"
we generate
yVL_CLOCK = 610, /* "/*verilator sc_clock*/" */
which is invalid since the comment will actually be closed on the
first "*/". Let's turn "*/" into "*\/" to avoid this. But GCC will
also warn about "/*" inside a comment, so let's "escape" it too.
Reported by Huang Rui.
https://github.com/akimd/bison/issues/38
* data/skeletons/c-like.m4 (_b4_comment): Escape comment delimiters in
comments.
* tests/input.at (Torturing the Scanner): Check thes cases.
* tests/m4.at: New.
Diffstat (limited to 'NEWS')
-rw-r--r-- | NEWS | 6 |
1 files changed, 6 insertions, 0 deletions
@@ -6,6 +6,12 @@ GNU Bison NEWS Some tests were fixed. + When token aliases contain comment delimiters: + + %token FOO "/* foo */" + + bison used to emit "nested" comments, which is invalid C. + * Noteworthy changes in release 3.6.1 (2020-05-10) [stable] ** Bug fixes |