Hi all,
This trivial patch fixes some spelling mistakes. If anyone has a
documentation or comment patch, I can put such minor patches
together and commit them in one go. I won't commit this for now,
just posting to notify the list first.
--
Cheers,
Kein-Hong Man (esq.)
Kuala Lumpur, Malaysia
di
Joshua Phillips wrote:
> Oughtn't tcc be broken into multiple source files?
I tried studying the sources over the weekend, and it looks like a
lot of functionality is mashed together, due to its "tiny"
heritage. So I think breaking up tcc.c would be a non-trivial
task. Perhaps worth a shot, though
LOL. You could break it into whatever organization you want. It seems
like tcc.c uses #include ".c" a lot. I like that usage, don't
you?
Joshua Phillips wrote:
Oughtn't tcc be broken into multiple source files?
___
Tinycc-devel mailing list
Tiny
Oughtn't tcc be broken into multiple source files?
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tinycc-devel
From: "Zdenek Pavlas":
> On Sun, Nov 25, 2007 at 10:13:08PM +, grischka wrote:
>
> > Reverted case label optimization
> > (See Changelog for details).
>
> > Last added case label optimization (455) produced wrong code.
> > Reverted.
>
> Have you some more information how to reproduce the b
From: "Marc Andre Tanner"
> Hi,
>
> It would be nice if you could make one commit per fix, it makes it
> easier to follow what's going on.
>
> Thanks,
> Marc
>
Okay, will TRY to do so.
And I know I interpreted your "hanging tcc -E" fix quite a bit
different. And actually I'm not even shure t
tcc does not provide such functions - they are provided by libc.
On Monday 26 November 2007 02:54:34 oyster wrote:
> as the title says, where is the random function?
> thanx
>
>
> ___
> Tinycc-devel mailing list
> Tinycc-devel@nongnu.org
> http://lists.n
On Sun, Nov 25, 2007 at 10:13:08PM +, grischka wrote:
Reverted case label optimization
(See Changelog for details).
> Last added case label optimization (455) produced wrong code.
> Reverted.
Have you some more information how to reproduce the bug?
Looked simple enough to
