>>92So you're saying TCC is incompatible with GCC? Quite likely, might be GCCs fault, though, too (yes, unlikely). In reality, a lot of compilers are probably binary incompatible with each other.
What I really think is that I'd guess that TCC produces correct code in terms of C compliance, but not POSIX/operating system compliance, i.e. it shits on ABIs and ``common standards''.
Just tested and I get both TCC and GCC compiled DLLs running in TCC-built exe.
Can't get TCC-built DLLs running in GCC, though -- don't know how to emit .a from TCC or create .a from .def in some way...
It segfaulted on me, while code compiled with [GCC?] didn't
Yes, 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.