Despite the fact we don’t actively develop `ldns`, our #DNS library for #clang, we're committed to providing bug fixes… Sometimes slowly, sometimes super fast... ⚡️

https://github.com/NLnetLabs/ldns/issues/287

LLVM-MOS – Clang LLVM fork targeting the 6502

https://llvm-mos.org/wiki/Welcome

#HackerNews #LLVM-MOS #Clang #LLVM #6502 #RetroProgramming #CompilerDevelopment

#llvm #clang help.

Anyone here knows what the difference is between builtin and standard include locations for LLVM/Clang ?

For some reason my LLVM install is using the C++ headers from the LLVM install tree and the system libc++, and I'd need it to using the system C++ headers for things to work.

Boost to fix compilation issues.

1. #Android kernels use #LLVM / #Clang almost exclusively. Clang supports two dialects: #GNU #C mode and #MSVC mode. Supporting both dialects means the kernel can build and test under more configurations.
2/3

The #Linux #kernel authorities are currently discussing whether to enable support for Microsoft C (MSVC) language extensions. Sounds like heresy? It turns out, this is about the growing importance of the #Clang compiler. The patches under review do not aim to compile Linux with Microsoft’s cl.exe compiler. Instead, they enable the kernel to take advantage of Clang’s ability to operate in a Microsoft-compatible dialect. Why would Linus Torvalds want that?
1/3

This is a simple space game.
I am making it in my spare time for fun and learning.
Feel free to use it as template for your own things.

https://sr.ht/~modevstudio/mospace/

#gamedev #clang #raylib #box2d #flecs

This is a simple space game.
I am making it in my spare time for fun and learning.
Feel free to use it as template for your own things.

https://sr.ht/~modevstudio/mospace/

#gamedev #clang #raylib #box2d #flecs

C++ library update in -current https://www.undeadly.org/cgi?action=article;sid=20250822171538 #openbsd #cplusplus #c++ #programming #development #library #clang #freesoftware #libresoftware

C++ library update in -current https://www.undeadly.org/cgi?action=article;sid=20250822171538 #openbsd #cplusplus #c++ #programming #development #library #clang #freesoftware #libresoftware

An interesting remark in Josep Bigorra's post on why Scheme can be used for production work:

There’s only one truly universal ecosystem: the C ecosystem. Dynamic language modules are often just bindings to existing C libraries.

https://jointhefreeworld.org/blog/articles/lisps/scheme-and-lisps-are-great-for-production/index.html

#lisp #scheme #clang

For two days straight, I just can't reproduce #swad #crashing with *anything* in place (#clang #sanitizer instrumentation, attached #debugger like #lldb) that could give me the slightest hint what's going wrong. 😡

But it *does* crash when "unobserved". And it looks like this is happening a lot sooner (or, more often?) when using #LibreSSL ... but I also suspect this could be a red herring in the end.

Situation reminds me of my physics teacher back at school, who used to say something in german I just can't ever forget:

"Wer misst, misst Mist."

Feeble attempt in english would be "the one who measures measures crap", it was his humorous way to bring one consequence of #Heisenberg's indeterminacy principle to the point. And indeed, #debugging computer programs always suffers from similar problems...

I need help. First the question: On #FreeBSD, with all ports built with #LibreSSL, can I somehow use the #clang #thread #sanitizer on a binary actually using LibreSSL and get sane output?

What I now observe debugging #swad:

- A version built with #OpenSSL (from base) doesn't crash. At least I tried very hard, really stressing it with #jmeter, to no avail. Built with LibreSSL, it does crash.
- Less relevant: the OpenSSL version also performs slightly better, but needs almost twice the RAM
- The thread sanitizer finds nothing to complain when built with OpenSSL
- It complains a lot with LibreSSL, but the reports look "fishy", e.g. it seems to intercept some OpenSSL API functions (like SHA384_Final)
- It even complains when running with a single-thread event loop.
- I use a single SSL_CTX per listening socket, creating SSL objects from it per connection ... also with multithreading; according to a few sources, this should be supported and safe.
- I can't imagine doing that on a *single* thread could break with LibreSSL, I mean, this would make SSL_CTX pretty much pointless
- I *could* imagine sharing the SSL_CTX with multiple threads to create their SSL objects from *might* not be safe with LibreSSL, but no idea how to verify as long as the thread sanitizer gives me "delusional" output 😳