People need just a reliable C compiler, that does only what was ordered to do.GCC isn't just a C compiler and was never meant to be. It was probably meant to be the only compiler installed on a system.
How so? Yes, as I said, it doesn't do wildcard expansion for example. But how does it produce broken code?It segfaulted on me, while code compiled with didn't. And calling TCC compiled code from GCC compiled code will give segfaults. Too lazy to research why it segfaulted and write a patch or a workaround.
It segfaulted on me, while code compiled with [GCC?] didn'tYes, might be that your code wasn't fully C compliant. As we all know, writing 100% correct C code is hard. Personally, I've had issues with code that returns structs from functions in TCC. Might be a C thing, not a TCC thing.
#include <stdio.h>
typedef struct meme {
int hax;
char anus;
} meme;
meme mememaker(int n, char c) {
meme ameme;
ameme.hax = n;
ameme.anus = c;
return ameme;
}
int main(void) {
meme kek = mememaker(5,'a');
printf("%d, %c\n", kek.hax, kek.anus);
} And it makes me wonder, a function can't return an array, but if a function can return a struct, can it just return a struct containing nothing but an array?I *guess* the issue here is that arrays can have unknown size while structs have fixed size -- which can be a problem when you want to have things returned on stack.
A function declarator shall not specify a return type that is a function type or an array type.So yes: structs allowed, TCC (seemingly) broken.
PS C:\Users\Adam> more anus.c
#include <stdio.h>
typedef struct meme {
int hax;
char anus;
} meme;
meme mememaker(int n, char c) {
meme ameme;
ameme.hax = n;
ameme.anus = c;
return ameme;
}
int main(void) {
meme kek = mememaker(5,'a');
printf("%d, %c\n", kek.hax, kek.anus);
}
PS C:\Users\Adam> tcc anus.c -o anus.exe
PS C:\Users\Adam> ./anus.exe
5, a
PS C:\Users\Adam> And it makes me wonder, a function can't return an array, but if a function can return a struct, can it just return a struct containing nothing but an array?Yes.
struct k {
char foo[256];
} myfunfunc() {
struct k ks = { "Foo!" };
return ks;
}struct k {
char foo[256];
} *myfunfunc(struct k *_ret) {
struct k ks = { "Foo!" };
memcpy(_ret, &ks, sizeof(ks));
return _ret;
}struct {int a; int x[];}; where the size isn't known? Also: what about Flexible array members in structs (since C99) like struct {int a; int x[];}; where the size isn't known?
(sizeof(int) + sizeof(int*)) but just sizeof(int).The sizeof operator on such a struct is required to give the offset of the flexible array member.
don't know how to emit .a from TCC or create .a from .def in some way...you don't need .a or .def to create a .dll with TCC. Just call tcc.exe with -rdynamic, -shared and -r, then load it from GCC compiled file with dlopen.
you don't need .a or .def to create a .dll with TCC.Not the problem.
tcc -shared foo.c generates both .dll and .def (assuming correct .c file)load it from GCC compiled file with dlopenMaybe I'll have a look into this today. On Windows it's
LoadLibrary() etc., right? On Windows it's LoadLibrary() etc., right?here is the implementation of dlopen for Windows