home.social

#tinycc — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #tinycc, aggregated by home.social.

  1. #Ducktinycc 'C' scripting in #Duckdb via #TinyCC Of course what better example than the embedded #RStats example from "Writing R extensions". With a bit more work (and threading issue stuff) this can be extended into some arbitrary R UDFs API for the r-duckdb Repo: github.com/sounkou-bioi...

  2. #Duckdb #TinyCC Ridiculous, dangerous but cool ! (very roundabout way to test out ideas of a potential api for a #RStats UDFs extension) Link for segfault lovers : github.com/sounkou-bioi...

  3. #tinycc based #RStats #C #Transpiler, only 4x slower than #{quickr} for the convolution benchmark ! 2-3x faster than naive #C + marshaling. #tinycc transpilation will have an obvious advantage since it can always fallback when transpiling and use `Rf_lang3` since it has access to R's C runtime !

    RE: https://bsky.app/profile/did:plc:hmk4f5yf3ohtsvw32sbtwvk3/post/3memwdbpbqs22

  4. Гений 21 века. Чем сейчас занимается Фабрис Беллар

    Некоторые программисты настолько хорошо известны, что не нуждаются в особом представлении. Наверное, Фабрис Беллар — самая яркая звезда современности. Автор мультимедийного комбайна FFmpeg, эмулятора QEMU и десятков других полезных программ — абсолютный гений и пример программиста 100х, который в одиночку принёс больше пользы миру, чем многие корпорации с сотнями разработчиков. В общем, все знают Фабриса — про него ещё была статья на Хабре двенадцать лет назад… … Но по просьбам молодых читателей мы решили вернуться к этой теме. Оно и к лучшему, ведь Фабрис многое сделал за это десятилетие, особенно в области нейросетей.

    habr.com/ru/companies/ruvds/ar

    #ruvds_статьи #Фабрис_Беллар #Better_Portable_Graphics #BPG #LZEXE #Harissa #число_Пи #Linmodem #FFmpeg #TCC #TinyCC #TinyGL #QEmacs #QEMU #формула_Беллара #QuickJS

  5. Гений 21 века. Чем сейчас занимается Фабрис Беллар

    Некоторые программисты настолько хорошо известны, что не нуждаются в особом представлении. Наверное, Фабрис Беллар — самая яркая звезда современности. Автор мультимедийного комбайна FFmpeg, эмулятора QEMU и десятков других полезных программ — абсолютный гений и пример программиста 100х, который в одиночку принёс больше пользы миру, чем многие корпорации с сотнями разработчиков. В общем, все знают Фабриса — про него ещё была статья на Хабре двенадцать лет назад… … Но по просьбам молодых читателей мы решили вернуться к этой теме. Оно и к лучшему, ведь Фабрис многое сделал за это десятилетие, особенно в области нейросетей.

    habr.com/ru/companies/ruvds/ar

    #ruvds_статьи #Фабрис_Беллар #Better_Portable_Graphics #BPG #LZEXE #Harissa #число_Пи #Linmodem #FFmpeg #TCC #TinyCC #TinyGL #QEmacs #QEMU #формула_Беллара #QuickJS

  6. @lispi314 sidenote: that #guile bootstrap path was developed for #guix :

    GNU Mes (maxwell equations of software) provides a minimal #scheme interpreter and C #compiler with tooling to build #tinycc that can be used with the Mes C library to compile glibc-2.2.5, binutils-2.20.1, gcc-2.95.3 with which you can build the whole #GNU system.

    Thanks to #GCCrs that will soon include #Rust

    Thanks to #Python on Guile it includes a shortcut for compatible Python-based tooling.
    #GCC
    @dalias @jschauma

  7. @ekaitz_zarraga and I have finally bootstrapped on starting from GNU and (and eventually tiny binary if you go further back).

    The binary that we have built is self-hosting and can build itself, though perhaps a few more bugfixes will be needed to reach the newest version of tcc.

    @janneke
    @efraim

  8. @janneke @aziz @fsf @fsfe @reproducible_builds @ekaitz_zarraga Indeed! Right now we can bootstrap all the way from to , then use to build very first build of (we can call it mes-tcc). mes-tcc can then build the next build of tinycc (boot0-tcc). Unfortunately, at the moment boot0-tcc segfaults. Today, I fixed one crash which was due to Global Offset Table being all zeros but it turns out we are now hitting another segfault, so more work is needed.

  9. Spent part of my at looking at bootstrapping 0.9.26 from on architecture. And thanks to mantainer @janneke for his help with debugging various issues. We can now build initial binary and it can even run some simple commands such as --help or -vv.

    Unfortunately, we still hit some critical bugs when trying to use this tcc binary to rebuild itself but hopefully we are not far now.



  10. @monk Why is it from . We have successfully bootstrapped kernel and userspace on x86 from far smaller binaries. E.g. builder-hex0 is about 200 bytes of code.

  11. @ekaitz_zarraga and I have finally bootstrapped #TinyCC on #RISCV starting from GNU #Mes and #MesCC (and eventually tiny #hex0 binary if you go further back).

    The binary that we have built is self-hosting and can build itself, though perhaps a few more bugfixes will be needed to reach the newest version of tcc.

    @janneke
    @efraim #bootstrappableBuilds
    #reproducibleBuilds

  12. @ekaitz_zarraga and I have finally bootstrapped #TinyCC on #RISCV starting from GNU #Mes and #MesCC (and eventually tiny #hex0 binary if you go further back).

    The binary that we have built is self-hosting and can build itself, though perhaps a few more bugfixes will be needed to reach the newest version of tcc.

    @janneke
    @efraim
    #bootstrappableBuilds
    #reproducibleBuilds

  13. @ekaitz_zarraga and I have finally bootstrapped #TinyCC on #RISCV starting from GNU #Mes and #MesCC (and eventually tiny #hex0 binary if you go further back).

    The binary that we have built is self-hosting and can build itself, though perhaps a few more bugfixes will be needed to reach the newest version of tcc.

    @janneke
    @efraim #bootstrappableBuilds
    #reproducibleBuilds

  14. @ekaitz_zarraga and I have finally bootstrapped #TinyCC on #RISCV starting from GNU #Mes and #MesCC (and eventually tiny #hex0 binary if you go further back).

    The binary that we have built is self-hosting and can build itself, though perhaps a few more bugfixes will be needed to reach the newest version of tcc.

    @janneke
    @efraim #bootstrappableBuilds
    #reproducibleBuilds

  15. @janneke @aziz @fsf @fsfe @reproducible_builds @ekaitz_zarraga Indeed! Right now we can bootstrap all the way from #hex0 to #Mes, then use #MesCC to build very first build of #tinycc (we can call it mes-tcc). mes-tcc can then build the next build of tinycc (boot0-tcc). Unfortunately, at the moment boot0-tcc segfaults. Today, I fixed one crash which was due to Global Offset Table being all zeros but it turns out we are now hitting another segfault, so more work is needed.

    #bootstrappableBuilds

  16. @janneke @aziz @fsf @fsfe @reproducible_builds @ekaitz_zarraga Indeed! Right now we can bootstrap all the way from #hex0 to #Mes, then use #MesCC to build very first build of #tinycc (we can call it mes-tcc). mes-tcc can then build the next build of tinycc (boot0-tcc). Unfortunately, at the moment boot0-tcc segfaults. Today, I fixed one crash which was due to Global Offset Table being all zeros but it turns out we are now hitting another segfault, so more work is needed.

    #bootstrappableBuilds

  17. @janneke @aziz @fsf @fsfe @reproducible_builds @ekaitz_zarraga Indeed! Right now we can bootstrap all the way from #hex0 to #Mes, then use #MesCC to build very first build of #tinycc (we can call it mes-tcc). mes-tcc can then build the next build of tinycc (boot0-tcc). Unfortunately, at the moment boot0-tcc segfaults. Today, I fixed one crash which was due to Global Offset Table being all zeros but it turns out we are now hitting another segfault, so more work is needed.

    #bootstrappableBuilds

  18. @janneke @aziz @fsf @fsfe @reproducible_builds @ekaitz_zarraga Indeed! Right now we can bootstrap all the way from #hex0 to #Mes, then use #MesCC to build very first build of #tinycc (we can call it mes-tcc). mes-tcc can then build the next build of tinycc (boot0-tcc). Unfortunately, at the moment boot0-tcc segfaults. Today, I fixed one crash which was due to Global Offset Table being all zeros but it turns out we are now hitting another segfault, so more work is needed.

    #bootstrappableBuilds