Conversation

🤔

an I wonder: would the LLVM libc be written in C++? Also, what would you call it? llibc? Logical next step is to have an LLVM kernel. What would you call that kernel? It would certainly be low-level, and would handle virtual machines (as well as virtual memory).

Quote Tweet

LLVM Weekly

@llvmweekly

Jun 25, 2019

Is it time for an LLVM libc? The Google LLVM team are collecting feedback lists.llvm.org/pipermail/llvm

Replying to

There could be so many more interesting LLVM projects to solve problems with existing platforms! - LLDE - the LLVM Desktop Environment - ALLSA - the Advanced LLVM Sound Architecture

Replying to

and

LLVM/Linux

Replying to

and

WSLL

Replying to

and

I wish I could take this as light-heartedly as yousall do, but Google already has its own libc, Bionic, and it's the crappiest of the crap software you can imagine calling itself a libc. They should work on perhaps improving that instead of polluting the space with one more.

Replying to

Don't forget the "crazy linker".

Replying to

The functionality to map libraries from an apk is part of the Bionic linker so Chromium's crazy linker hasn't been relevant for a long time. They use the standard linker on any remotely modern platform. It was a bit nuts to have a custom linker in Chromium so that name was good.

Replying to

I remember it fondly. Digit tried to convince me to LGTM the review 😓

Replying to

It's a fairly boring OS feature implemented within the standard linker now. It's used by setting android:extractNativeLibs="false" in the manifest which is being recommended as a way for app developers to save storage space: developer.android.com/topic/performa. It has other benefits though.

developer.android.com

Reduce your app size | Android Developers

9:27 PM · Jun 25, 2019Twitter Web Client