Uff!
"jemalloc Postmortem", Jason Evans (https://jasone.github.io/2025/06/12/jemalloc-postmortem/).
Via HN: https://news.ycombinator.com/item?id=44264958
On Lobsters: https://lobste.rs/s/thpska/jemalloc_postmortem
#Malloc #Libc #jemalloc #MemoryManagement #Retrospective #OpenSource #FOSS #Facebook #Meta #FreeBSD #Linux #Windows #Allocators
folks who do smart things with multiprocessing models like Go and Chromium usually don't want C libraries potentially stepping on their toes. Oh gosh threads. The day I figure out how to do those, will be day the whole world will want to use this thing. But I want people who use Cosmopolitan #Libc to know what value it's providing them. I think the best way to do that is by raising awareness of the systems engineering fundamentals like this. Because that's something you're right to point out that the #Linux community leadership has room for improvement on.
https://news.ycombinator.com/item?id=26290723
@MichaelRoss something I have been trying to look for is a #Linux #ls that isn't depending on #glibc or another #libc implementation, the reason is there was some malware that attached itself to glibc and prevented you to see the directories and files it used and also the process directory in /proc
Had you a ls that wasn't built with glibc, then all the files and directories would be listed.
#BSI WID-SEC-2025-1089: [NEU] [hoch] #GNU #libc: Schwachstelle ermöglicht Codeausführung
Ein entfernter, anonymer Angreifer kann eine Schwachstelle in GNU libc ausnutzen, um beliebigen Programmcode auszuführen.
https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2025-1089
Comparison of C/POSIX standard library implementations for Linux
https://www.etalabs.net/compare_libcs.html
#HackerNews #C #POSIX #Linux #Comparison #Libc #Implementations #Programming
(bits) of a Libc, Optimized for Wasm
https://github.com/ncruces/go-sqlite3/tree/main/sqlite3/libc
#HackerNews #Libc #Wasm #Optimization #WebAssembly #GoSQLite3
[Перевод] Ужасное состояние двоичной совместимости Linux (и что с ним делать)
Двоичная совместимость в Linux омрачена одним аспектом, который часто упускаю из виду при рассмотрении выпуска ПО для Linux. В этой статье я расскажу, как можно увидеть этот аспект, как решать эту проблему при выпуске современного ПО и что же именно нужно сделать, чтобы устранить её полностью.
https://habr.com/ru/articles/893720/
#двоичная_совместимость #дистрибутивы_linux #linux #libc #стандартная_библиотека
Since the value returned by `time(2)` is corrected for leap seconds by NTP (for good reason, but still), time doesn't mean anything since it isn't doesn't represent a unique instant, which also means you can't do math with it (which you need to do for timezone correction).
I.e. as long as everything you're building upon is based off `CLOCK_REALTIME`, you are working with a shaky framework of heuristics
把 libc 移植到 GPU 上跑
在「Using Libc for GPUs (llvm.org)」這邊看到的，本來在想是個路人的噱頭 project，但仔細看才發現是 LLVM libc 官方的文件：「Using libc for GPUs」。
不是所有的 libc 函數都被 porting 上去，但從列出來的支援清單可以看到主要就是計算類會用到的，但還是有包括一些 I/O (stdio.h) 與時間 (time.h) 相關的函數：
Once you have finished building the GPU C library it can be used to ru
#Computer #Murmuring #Programming #Software #gpu #libc #llvm
Something I would like to make in #rust is a #libc wrapper that uses type-level contracts and optional (maybe debug-by-default) runtime checks. I like Rustix, but I'd like to make something that you can use with magnitudes less footguns.
If you know of a company/team that would be willing to fund such work, I'd be eager to get connected!
#FediHire #contracting
(Please reply with suggested hashtags, I'm not the greatest at these xD)
To enable fast system calls in dynamically linked binaries, we load at runtime a C library that is "unikernel-aware" and employs function calls into the kernel for system calls invocations. This C library is a special version of Musl #libc that can be created fully automatically from vanilla Musl. This is done with the Coccinelle code transformation tool. To build it and test it out, use the following steps.
https://github.com/ssrg-vt/hermitux/wiki/Fast-system-calls-in-dynamically-linked-programs
system call interface is designed to be compatible with the C calling convention, which is also the most common calling convention used globally. By adhering to the C calling convention, developers can not only perform system calls in different programming languages, they can also call procedures written in another language, because most languages use C calling convention for their FFI feature. The latter case is even more common, as most languages won’t interact with the system call interface directly in binary level, but by calling a C-based system call wrapper defined in the #libc
this ABI is painfully difficult to disentangle from the programming language C. In order to make a C call, you don’t just need to know what registers to pass arguments in and what size an int is, you need to know things like struct layout and what it means to spill a struct onto the stack. You also need some way to take the interface specifications provided by operating systems and turn them into a format your compiler can work with, and wouldn’t you know it, those interface specifications are provided in the form of… C header files.
https://langdev.stackexchange.com/questions/3233/why-do-common-rust-packages-depend-on-c-code/3237#3237
Ukrywanie procesów za pomocą ld.so.preload ( https://nfsec.pl/security/6505 ) #linux #security #libc #preloading #twittermigration
#TIL J'ai découvert https://justine.lol/cosmopolitan/index.html
Un outil pour compiler du #C vers un format capable de s'exécuter partout : Linux, Windows, Mac, FreeBSD... ARM64 et x86_64, sans reposer sur une plateforme (comme la #JVM) ni sur un interpréteur (comme #Python)
Il y a un article qui détail comment ça fonctionne (je n'ai que lu la moitié parce que je ne comprennais pas, c'est trop bas niveau) https://justine.lol/ape.html
#Dev #CrossCompilation #Compilation #APE #Cosmopolitan #LibC #GCC
