Re: [Tinycc-devel] Question about in-memory compilation, target

2024-02-10 Thread Michael Richter via Tinycc-devel
This means, that not only the public API changes, but also the libtcc.dll/so ABI, making all programs using libtcc crash without warning. Is this intended? Michael Ok, I like it to remove stuff: https://repo.or.cz/tinycc.git/blob/b671fc0594625eb5ac147ec83be6d0c1fc1a6ad5:/libtcc.h

Re: [Tinycc-devel] Question about in-memory compilation, target

2024-02-10 Thread Eric Raible
> This means, that not only the public API changes, but also the > libtcc.dll/so ABI, making all programs using libtcc crash without warning. > > Is this intended? > > Michael I just tried it. It looks like only programs that _don't_ use TCC_RELOCATE_AUTO would be affected (at least on my

Re: [Tinycc-devel] Question about in-memory compilation, target

2024-02-10 Thread Eric Raible
I've just taken a closer look at libtcc.h. Now, I realize that this is radical, but for the sake of discussion... if we're willing to break compatibility it seems to me that just one new API: /* add option as on a comment line (multiple supported) */ LIBTCCAPI int tcc_argv_add(TCCState *s, const

Re: [Tinycc-devel] C versions (was Re: Re : Re: Re : Re: Where do I get pthread.h?)

2024-02-10 Thread Страхиња Радић
On 24/02/10 12:33PM, gz8...@0w.se wrote: > Thus, if I might ask Tiny CC developers for a favor, as far as possible, > please do not use C99 or later features in Tiny CC itself. This feature is important for tcc to be able to replace GCC and Clang, because a number of existing real-world packages