Unrelated to cross-compiling, with regards to 128bit datatype support this raises a few more questions than answered. Recalling some wikipedia reading ancient DEC VAX (32bit system) was capable of emulating full 128bit data type support (with help from hardware and/ or compilers used in 1980s already). I too recall GCC had implemented some 128bit general purpose data-type support for some but not all ARCH (sort of emulation by compiler/libgcc?)
Now the principle questions would be: - which ARCH could have emulated 128bit data types (with the help from libtcc?) - why aarch64 got those, and riscv64 hasn't got them (is that specific to tcc?) - and which ARCH=x86_32|64|aarch32|64|etc. could have 128bit general purpose data type support offered with tcc - and referring back to the initial post in case of riscv64 why it hasn't got uint128_t if i didn't mis-interpret the report Of cause, emulating 128bit data types on a 32bit data-bus system would be slowler, nonetheless there had not been any reason to restrict data-types ever since when DEC VAX showcased it's been feasible to do so in 1980s ever since. On 2026-01-29 12:01, grischka via Tinycc-devel wrote: > > For example. arm64-tcc knows __uint128_t, but riscv64-tcc does > not. (See include/tccdefs.h) > > > -- gr > > > _______________________________________________ > Tinycc-devel mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/tinycc-devel -- aggi
signature.asc
Description: Digital signature
_______________________________________________ Tinycc-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/tinycc-devel
