#mescc — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #mescc, aggregated by home.social.
-
The original sin of computing ... that no one can fix: https://youtube.com/watch?v=Fu3laL5VYdM&si=zZmUAGORG9yCW5Yn And you are not even mentioned @janneke although the graph displayed around 18:55 shows
#mes and #mescc. -
The original sin of computing ... that no one can fix: https://youtube.com/watch?v=Fu3laL5VYdM&si=zZmUAGORG9yCW5Yn And you are not even mentioned @janneke although the graph displayed around 18:55 shows
#mes and #mescc. -
@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.
-
@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.
-
@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.
-
@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.
-
@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 @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.
-
@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.
-
@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.
-
@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.
-
@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.
-
@janneke and I were trying to fix 64-bit (#amd64 for now) #GnuMes bootstrap. After applying some fixes to M2-Planet and #mes we were able to bootstrap mes-m2 binary from #hex0. And it's working well enough to rebuild itself with #mescc.
This is expected to be in the next releases of mes 0.25 and M2-Planet 0.11.
-
@janneke and I were trying to fix 64-bit (#amd64 for now) #mes bootstrap. After applying some fixes to M2-Planet and #mes we were able to bootstrap mes-m2 binary from #hex0. And it's working well enough to rebuild itself with #mescc.
This is expected to be in the next releases of mes 0.25 and M2-Planet 0.11.
-
@janneke and I were trying to fix 64-bit (#amd64 for now) #GnuMes bootstrap. After applying some fixes to M2-Planet and #mes we were able to bootstrap mes-m2 binary from #hex0. And it's working well enough to rebuild itself with #mescc.
This is expected to be in the next releases of mes 0.25 and M2-Planet 0.11.
-
@janneke and I were trying to fix 64-bit (#amd64 for now) #mes bootstrap. After applying some fixes to M2-Planet and #mes we were able to bootstrap mes-m2 binary from #hex0. And it's working well enough to rebuild itself with #mescc.
This is expected to be in the next releases of mes 0.25 and M2-Planet 0.11.
-
@janneke and I were trying to fix 64-bit (#amd64 for now) #mes bootstrap. After applying some fixes to M2-Planet and #mes we were able to bootstrap mes-m2 binary from #hex0. And it's working well enough to rebuild itself with #mescc.
This is expected to be in the next releases of mes 0.25 and M2-Planet 0.11.
-
Just like in the case of #CollapseOS or the #Guix minimal bootstrap project with #stage0 , #mes and #mescc that means cutting down on complexity and rebasing the history of actual events, so that iterations can.be short-circuited and the chain from very low technological sophistication to the level that can fulfill the task can be kept as short as possible. -
Just like in the case of #CollapseOS or the #Guix minimal bootstrap project with #stage0 , #mes and #mescc that means cutting down on complexity and rebasing the history of actual events, so that iterations can.be short-circuited and the chain from very low technological sophistication to the level that can fulfill the task can be kept as short as possible.