Re: [f-cpu] C/VHDL code and fcpusim

[Yann Guidon <whygee@f-cpu.org>]

hi,

Christophe Avoinne wrote:
> 
> I could be helpful regarding with flex or bison. What the trouble with the
> memory allocation ?

it's not a problem with Bison and Flex (they are solved for a long time now).

the problem is that there is a quantity of different kinds of data
with different properties, some are allocated once and remain until the
end of the program (ie : the binary code), some structures are more
complex (a file descriptor stack for the includes, a #define list of
symbols etc) and some are even worse.

so i have to find the best algorithm and structure for each case.
The goal is to avoid memory leaks and unused regions, so the computer
doesn't run out of memory when compiling something like X11 or Mozilla...
(just in case it's used to do that).

WHYGEE
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
*************************************************************
To unsubscribe, send an e-mail to majordomo@seul.org with
unsubscribe f-cpu       in the body. http://f-cpu.seul.org/