FYI a moment ago pnut-exe announced an update on github to compile latest
tcc version:
https://github.com/udem-dlteam/pnut/pull/249

"
   Pnut has been able to compile TCC-bootstrap (based on 0.9.26) for some time. 
That version of TCC was patched to work around the lack of 64-bit integers in
   bootstrap compilers (MesCC/pnut before #248) and floating point numbers. 
Bootstrapping 64-bit integers and floating point numbers required a significant
   number of patches, and multiple compilation steps to reach a fixed point, 
and is hard to understand.

   This PR builds on #248 to build the last TCC release , version 0.9.27. 
Because 64-bit integers are supported, only floating point numbers and 4 small
   thingsneeds to be patched:

     * bitfields
     * __attribute__
     * array[sizeof ...] declaration
     * missing scanf libc function
"

There is a good chance now related changes can help with keeping tinycc mob/HEAD
bootstrappable/compilable by pnut-cc too, which then can significantly shorten
the dependency chain without an intermediate 0.9.26 version.

Only limitation of this approach would be mes-cc not yet cannot remain a
drop-in replacement for pnut-cc anylonger to compile tcc-0.9.27 or HEAD.

And tinycc 0.9.27/HEAD would need some patching, and of cause this whole
approach needs testing and confirmation still.

On 2026-07-14 17:29, Michael Ackermann via Tinycc-devel wrote:
> 
> On 2026-07-13 14:18, Ivo van Poorten wrote:
> > On the other hand, the hex0 to tcc-0.9.26/janneke bootstrap is a fully
> > verifiable source path.
> 
> Yes, hence I only allowed myself to argue the issue with tcc-0.9.26 should be
> kept in mind, since this is the most plausible solution (without any other 
> known
> currently). No idea why tccm is denying this. I have no clue at all either why
> tccm argues for VSOBFS which neither adresses a complete system-bootstrapping
> option nor C-standard followed and language features relied upon related to 
> this.
> 
--

Attachment: signature.asc
Description: Digital signature

_______________________________________________
Tinycc-devel mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/tinycc-devel

Reply via email to