[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: performance bottleneck in yy_get_next_buffer function
From: |
Hans Aberg |
Subject: |
Re: performance bottleneck in yy_get_next_buffer function |
Date: |
Tue, 15 Jan 2013 10:28:33 +0100 |
On 15 Jan 2013, at 09:57, Gautam Kapoor <address@hidden> wrote:
> This is true both for flex and flex++.
>
> Yes, my patch fixed that problem. Ideally, I would expect memcpy to be used
> instead of a for-do there. But Martin (attached email) suggests that it could
> be fixed by changing the buffer size. I have to try that. If one can choose
> an optimal buffer size (may not always be possible), then the effect of this
> for-do will be minimized.
The problem seems to be buffer implementation problem. So making it larger
might work for a particular lexer but it does not fix the problem in Flex.
Hans