Conversation

Notices

1. Embed this notice
   datenwolf (datenwolf@chaos.social)'s status on Friday, 19-Jun-2026 04:57:15 JST datenwolf

   • Rich Felker

   @dalias

   What's your stance on including the/some tinycc-musl-support patches into mainline musl?

   • Embed this notice
     Rich Felker (dalias@hachyderm.io)'s status on Friday, 19-Jun-2026 04:57:11 JST Rich Felker

     in reply to

     @datenwolf It probably depends on what they look like and whether the support would actually produce a working build or something halfass and buggy.

   • Embed this notice
     Rich Felker (dalias@hachyderm.io)'s status on Friday, 19-Jun-2026 04:57:42 JST Rich Felker

     in reply to

     @datenwolf In any case it's worth submitting them as a starting point for discussion. It might turn up other ways to achieve the same thing, or fixes that should be made to tinycc.

   • Embed this notice
     Rich Felker (dalias@hachyderm.io)'s status on Friday, 19-Jun-2026 05:04:46 JST Rich Felker

     in reply to

     @datenwolf On first glance, there's a lot there that seems unmotivated. I think you'd need to figure out what was the intent of a lot of those changes.

   • Embed this notice
     datenwolf (datenwolf@chaos.social)'s status on Friday, 19-Jun-2026 05:04:54 JST datenwolf

     in reply to

     • Rich Felker

     @dalias

     The starting point I'd approach this from would be this repository

     https://github.com/GataOS/musl-tcc

     Do a merge / rebase against latest musl, look at the diff to musl upstream and clean up and rewrite anything I don't like. If / where necessary introduce conditional compilation blocks active only when used by/with tcc.

   • Embed this notice
     Rich Felker (dalias@hachyderm.io)'s status on Friday, 19-Jun-2026 05:26:01 JST Rich Felker

     in reply to

     @datenwolf Sorry, I meant motivations for individual changes in that repo. It doesn't seem to be documenting why they did half of the stuff they did.

   • Embed this notice
     datenwolf (datenwolf@chaos.social)'s status on Friday, 19-Jun-2026 05:26:02 JST datenwolf

     in reply to

     • Rich Felker

     @dalias

     My main motivation is building a compiler boostrap ladder.

     tcc → tcc.static → tccmusl.static → tcc.static-tccmusl → gcc4.9.static-tccmusl → musl.static → gcc4.9.static-musl → musl → gcc4.9-musl

     From there it should be mostly straightforward to climb the ladder of every major GCC version, and also branch out into LLVM/clang and glibc.