IRC channel logs
2026-02-16.log
back to list of logs
<aggi>last qemu-version seems qemu-0.14.1 year-2011 <aggi>gladly there's gentoo archives which collected older ebuilds for this <aggi>qemu is an exemplary case too, how such an important piece of software got overloaded with lines-of-code and features <aggi>version 0.1x source bundle is ~3MiB in size, version 2.x is 30Mib in size, and nowadays it's 150MiB - for source files <aggi>the old versions already did support many architectures, but to have support for riscv64/aarch64 etc you must pull in all the other bloat with it <aggi>next it will be interesting to see, of cause, if such an old version actually compiles with i386-tcc <aggi>having a glimpse at both qemu-0.9.1 and 0.14.1 i'm not yet sure if i picked the latest <aggi>since 0.9 ./configure got a handful of options, 0.14 got dozens of them <aggi>but they're otherwise equal with relevant architectures available <aggi>i'm only little sad, there's no aarch64/riscv64, since this will complicate a system-integration setup for arm64-tcc and riscv64-tcc <aggi>because tcc can't self-host this <aggi>current situation then, it's unavoidable to pull in hundreds of millions of lines of code for toolchain and dependencies to spawn a qemu for these <aleksih>It seems MesCC used to have symbol table support but not anymore. I'm struggling in gdb without symbols, so maybe we could add it in again? <aleksih>That is, ELF string and symbol table generation <aleksih>Oh, I may just be wrong, there is blood-elf? <matrix_bridge><Andrius Štikonas> Perhaps there are some bugs, especially on non x86 arches <aleksih>Yes, it seems to work pretty well. Admittedly I never tried using -g <aggi>QEMU.static 0.14.1 passed compilation/linking with i386-tcc for integration into TinyCC/Linux2 OS <aggi>runtime-testing ahead...