Daniel Glöckner wrote:
[...]
I think he eventually fixed it:
http://lists.gnu.org/archive/html/tinycc-devel/2006-12/msg00020.html
Doesn't help, I'm afraid --- although it would appear that the changes
never *did* make it into CVS...
Turns out that at least some of my problems are due to a
Heyas all,
First of all, might I suggest some warnings in libtcc.h? It seems to
suggest that you
can allocate as many compiler states with tcc_new() as you want and
none will mess
with each other-- I was in for a shock when I looked at the code and it was
sapping globals left and right! from tcc
From: egodust:
Heyas all,
First of all, might I suggest some warnings in libtcc.h?
Maybe a TODO entry?
I was in for a shock when I looked at the code and it was
sapping globals left and right! from tcc state :(
True.
Be that as it may, I was hoping to use libtcc to compile a set of
C
From: David Given:
Daniel Glöckner wrote:
[...]
I think he eventually fixed it:
http://lists.gnu.org/archive/html/tinycc-devel/2006-12/msg00020.html
Doesn't help, I'm afraid --- although it would appear that the changes
never *did* make it into CVS...
Hm, should we have that? Or better
Heyas,
On Thu, Apr 17, 2008 at 9:16 PM, grischka [EMAIL PROTECTED] wrote:
First of all, might I suggest some warnings in libtcc.h?
Maybe a TODO entry?
:)
I was in for a shock when I looked at the code and it was
sapping globals left and right! from tcc state :(
True.
Be
