https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92008
--- Comment #22 from Akim Demaille ---
FWIW, the version in the glibc was updated to use "%parse-params" and "%define
api.pure full" five years ago.
https://sourceware.org/git/?p=glibc.git;a=blob_plain;f=intl/plural.y;hb=6d248857845aee307440a770
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92008
Jim Wilson changed:
What|Removed |Added
CC||wilson at gcc dot gnu.org
--- Comment #21 f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92008
--- Comment #20 from Jakub Jelinek ---
Forgot an important part:
--- config/gettext.m4.jj2020-01-12 11:54:35.753423366 +0100
+++ config/gettext.m4 2020-04-16 12:34:51.466081569 +0200
@@ -1,5 +1,5 @@
# gettext.m4 serial 20 (gettext-0.12
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92008
--- Comment #19 from Jakub Jelinek ---
Created attachment 48287
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48287&action=edit
gcc10-pr92008.patch
Or maybe just do require bison 3 (7 years old) if intl/plural.y needs to be
regenerated?
D
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92008
--- Comment #18 from Akim Demaille ---
WRT to "pure-parser", there seems to be some misunderstanding. News of 3.4
says:
The %pure-parser directive is deprecated in favor of '%define api.pure'
since Bison 2.3b (2008-05-27), but no warning wa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92008
--- Comment #17 from Akim Demaille ---
Hi Jakub,
I'm not claiming you should require 3.0, I'm claiming there's no reason to
target 1.35, there is no evidence there's a need for it. So there's no reason
to pay for "PARSE_PARAMS" support.
"%requ
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92008
--- Comment #16 from Jakub Jelinek ---
bison 1.35 doesn't, and that is what has been used last time.
Is even %define api.pure full (vs. %pure_parser) supported in much older bison
versions? Maybe 1.875 is the oldest people do use in real-world,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92008
--- Comment #15 from Akim Demaille ---
Sorry to insist, but I don't understand all these complications. Bison has
been supporting %parse-param for 17 years.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92008
--- Comment #14 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:437eea66a4b010d8e94aa81c2b40ccf0588e5fab
commit r10-7752-g437eea66a4b010d8e94aa81c2b40ccf0588e5fab
Author: Jakub Jelinek
Date: T
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92008
--- Comment #13 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:2ca17e0a89ff6c37e17851a5bd7b0a03ee8de535
commit r10-7748-g2ca17e0a89ff6c37e17851a5bd7b0a03ee8de535
Author: Jakub Jelinek
Date: T
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92008
Akim Demaille changed:
What|Removed |Added
CC||akim.demaille at gmail dot com
--- Comme
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92008
Jakub Jelinek changed:
What|Removed |Added
Last reconfirmed||2020-04-15
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92008
--- Comment #10 from Richard Biener ---
(In reply to Jakub Jelinek from comment #9)
> Wouldn't it be better to git mv plural.y plural.y.in and depending on bison
> >= 3 or earlier just with sed tweak it (and in configure detect bison
> version, o
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92008
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #9
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92008
--- Comment #8 from Andrew Pinski ---
(In reply to fdlbxtqi from comment #7)
> (In reply to Andrew Pinski from comment #6)
> > https://github.com/zerovm/glibc/commit/9f3f5229848390ae921f77c92f666ca6f0bff
> >
> > is more the correct fix.
> > Or u
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92008
--- Comment #7 from fdlbxtqi ---
(In reply to Andrew Pinski from comment #6)
> https://github.com/zerovm/glibc/commit/9f3f5229848390ae921f77c92f666ca6f0bff
>
> is more the correct fix.
> Or use an older version of Bison.
But I am using windows.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92008
--- Comment #6 from Andrew Pinski ---
https://github.com/zerovm/glibc/commit/9f3f5229848390ae921f77c92f666ca6f0bff
is more the correct fix.
Or use an older version of Bison.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92008
--- Comment #5 from Andrew Pinski ---
Looks like the problem is with Bison 3.0 and above with the internal intl
BASH has/had the same issue:
https://savannah.gnu.org/support/?109469
18 matches
Mail list logo
