From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Michael Meskes <meskes(at)postgresql(dot)org> |
Cc: | PostgreSQL Hacker <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: bison news |
Date: | 2002-08-20 15:10:01 |
Message-ID: | 6504.1029856201@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Michael Meskes <meskes(at)postgresql(dot)org> writes:
> I just got the latest beta and it compiles ecpg grammar correctly!
This is good. Any word on when it will go to an official release?
BTW, I spent some time looking at the problem, and it seems the issue
is not overrun of any bison internal table, but failure to compress the
resulting "action table" into 32K entries. This means that the required
expansion from short to int is not just a cost paid while you run bison;
the actual table in the ecpg executable will double in size. I trust
they did not fix the problem in a way that causes *every* generated
parser to use an int[] rather than short[] action table ...
Also, it seemed to me that the most leverage on the size of the
compressed action table would be gained by reducing the number of
terminal symbols, more so than the number of rules. Dunno if there
is a lot you can do about that, but it's a thought.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-08-20 15:13:38 | Re: @(#) Mordred Labs advisory 0x0001: Buffer overflow in |
Previous Message | Tatsuo Ishii | 2002-08-20 15:08:37 | Re: @(#) Mordred Labs advisory 0x0001: Buffer overflow |