grischka wrote
Better leave alone tcccoff.c too. Other than that I think it
makes sense. You could test with
$ make clean && make all cross ONE_SOURCE=yes
and with "no" too.
I followed these instruction, and dumped symbol table of all object files. I
found more function has scope problem
I'm sorry to send a duplicate mail by mistack a short while ago.
what I really want to say is that I make a patch to add all missing scope
modifier .
Static scope is userful when use ONE_SOURCE build mode, which can avoid
unexpected name confilict.
The patch show below:
https://github.com/
-- Original --
From:
"Ekaitz Zarraga"
https://lists.nongnu.org
In my opinion, as tcc do not offer the complete libc on unix-like os, Current
Windows support in tcc which help tcc compile itself is enough. We can
recommand user to use tcc with compatible c library (like
"mingw","msvc","windows sdk"?) for other os-dependent feature.
I'm not familiar with Wi
This bug may caused by "vpushv" SValue with VT_CMP flag. There should be only
one VT_CMP SValue on vstack.
I make below patch to fix it, then the compilation exit normally. But
I have no arm64 device with GNU/Linux to verify the test.
diff --git a/arm64-gen.c b/arm64-gen.c
index 6389409..a9cb
