First of all : Hello.
I really rarely answer (when I unexpectedly could), BUT :
with tcc, this (test.c)
#include
#include
int main(void) {
printf("%d\n", PTHREAD_PRIO_NONE);
return 0;
}
|compiles and ouputs :|
|ian@KsyNET-0:~$ tcc -run test.c
0
ian@KsyNET-0:~$
|
|Furthermore, I
Indeed, I'd say focus on more up to date and elaborate programming languages.
C, while nice as a "portable assembler" is still full of quirks and tricks.
Which show how unstable and unprofessional it is 50 years after its creation.
Many "extensions" and as you state, "unfortunately" packaged by
Not trolling, I love C, and even more so assembler.
But let's face it, "C" as a language is spawned into many incarnations.
All barely compatible with each other, unless you stick to C89. If so.
About libraries, pthread is not even present on Windows, unless Cygwin or so.
To progress you have
I was trying to compile a program that requires pthread.h (which is a
header file that comes with GCC by default, and I thought that TCC was
supposed to be GCC compatible) but TCC is missing pthread.h unfortunately.
So I can't compile the program who's source code I downloaded, because its
source
Hi TinyCC follower.
The current branch is a release candidate for TinyCC 0.9.28 since some month.
From the active people here, only grischka has the rights to make a release,
and I suggest, that we should help him to be comfortable to make a release by:
* more testing
* add only minimal fixes
I push a patch for stdatomic.c , use a MemoryBarrier macro define for it.
And the code has been tested under GCC and MSVC.
- 原始邮件 -
发件人：Detlef Riekenberg via Tinycc-devel
收件人：tinycc-devel@nongnu.org
抄送人：Detlef Riekenberg , gr1...@gmail.com, Eric Raible
, kbkpbot
主题：[Tinycc-devel] Recent
Detlef,
Thanks for taking the time to respond! I'm new here, and still finding my
way around.
Let me respond to everything:
> A custom allocator is not a new idea. TinyCC has already a custom
allocator and uses it by default.
I
'm using libtcc in my application, and I didn't see a way to tell
