#DevLog: #Anklang Binding Migration

Trying to base the C++ <-> JSON bindings on `#clang -extract-api` instead of castxml

Have prototype code for #JSON call dispatching

Atm fighting #CPlusPlus template specializations for member func with and w/o const

The ultimate goal is to make the bindings type safe with #Typescript wrappers

I have just set the first video public from our #LLVM #Meetup in #Darmstadt.

Expect to see more and more videos coming online as we bring online all our recordings.

Check it out: Sebastian Kreutzer - Selective Instrumentation with XRay [LLVM Meetup Darmstadt]
https://youtu.be/bgWWzA3n3Jk

#HPC #Clang
@llvmweekly
@llvm

If anyone needed that data point, #Flang build (using #Clang on AArch64) with -j96 peaks at 102 GiB RAM use.

Optimization in action!

After fine-tuning core layers in MocaccinoOS (with selective -O3, clang, LTO, and --gc-sections), Geekbench scores improved significantly on my Ryzen 5 5600:

Single-core: +7.1%
Multi-core: +7.6%

From 2026 → 2169
From 8877 → 9552

Not bad for just smarter builds!
#Linux #Gentoo #MocaccinoOS #Optimization #Geekbench #clang #LTO

And I'm not done yet.

I like to think of Arch Linux in the same way the C programming language gives you the freedom to royally screw things up if you don't know what you're doing, and NixOS in the same way that the Rust programming language provides safety to prevent you from easily making stupid mistakes.

What do OpenBSD people use for static analysis of C code?

Valgrind was available for a while but it seems to have been removed now

Apparently there is something called the "Clang Static Analyzer", but I'm not sure how to actually use it (it seems you have to compile your program with specific Clang flags?)

I know there are countless other bugs in my code, but its nice to see "no leaks detected" when I do some stupid shit with void pointers :)

How do you use #jails on #FreeBSD as a software engineer? Does it make sense to keep my "host" clean and minimal and for example as a #cpp developer have two jails to compile code with #gcc and other one with #clang?

Evolution of the C #ProgrammingLanguages #CProgramming #CProgrammingLanguage #CLang #Programmer #Programming #SoftwareDeveloper #SoftwareDevelopment #Coder #Coding #CSharp #CPP #CPlusPlus #GCC #DotNet.

[some] 2025 AsiaLLVM videos are up!
(There will probably be more videos uploaded & added to this playlist over the next week or so.)
#LLVM #Clang
https://www.youtube.com/playlist?list=PL_R5A0lGi1ADKfJbzpA0rMDCb5T3QGe5k

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

Go home, Clang, you are drunk!

morning brings a clang
a shrill big thrill of a bang
my alarm, the cat

#haiku #poetry #writing #PoetryCommunity #WritingCommunity

#MastoPrompt #clang
@stevencudahy

The #MastoPrompt for Tuesday 24 June 2025 is:

#clang

The poem or story can include the prompt word or be about the prompt word.

@ me, if you like, or just include the #MastoPrompt tag (to allow people to follow or filter their feeds), or keep your work to yourself - all the options are good as long as you're writing.

If you're including an image please do include alt-text if you’re able to.

Now that I finished the #Clang backend of the topic (a CPU/GPU , through #openMP, accelerated library for managing bitsets) for the summer conference community talk (https://www.papercall.io/perlcommunity) in 15 days, I find that I will probably have no time to complete the #Perl front-end before the deadline.
Lessons learned :

1. Reference counting kicks ass (it's the default way to manage memory mappings for the GPU with #openMP), especially if one can control when the memory is released back to the pool

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

c/c++ devs of fediverse, what does your debugging workflow look like? I've used gdb manually a bit but it's quite laborious to set up each session. I need to be able to do step-through debugging with variable inspection.

[VS]Code and studio are very good for step through debugging once they're set up, but I'd rather avoid them altogether if possible, especially since you have to jump through a series of flaming hoops to get c debugging working in the non-telemetry open source version of code.

Any/all suggestions appreciated, other than 'use rust' #programming #clang #cpp

clang(1)/llvm/lld(1) updated to version 19 https://www.undeadly.org/cgi?action=article;sid=20250612123207 #openbsd #clang #llvm #lld #development #compiler #update

Fabien Sanglard published a blog series on driving C compilers, i.e. running the compiler toolchain to build executable programs:

https://fabiensanglard.net/dc/index.php

More recently Julia Evans @b0rk posted on the related topic of using Make to compile C programs, which nicely complements Fabien's series:

https://jvns.ca/blog/2025/06/10/how-to-compile-a-c-program/

Part1: #dailyreport #cuda #nvidia #gentoo #llvm #clang
#programming #gcc #c++ #linux #toolchain #pytorch

I am compiling PyTorch with CUDA and CUDNN. PyTorch is
mainly a Python library with main part of Caffe2 C++
library.

Main dependency of Caffe2 with CUDA support is
NVIDIA "cutlass" library (collection of CUDA C++
template abstractions). This library have "CUDA code"
that may be compiled with nvcc NVIDIA CUDA compiler,
distributed with nvidia-cuda-toolkit, or with LLMV
Clang++ compiler. But llvm support CUDA only up to 12.1
version, but may be used to compile CUDA for sm_52
architecture. Looks like kneeling before NVIDIA. :)

Before installing dev-libs/cutlass you should do:
export CUDAARCHS=75

I sucessfully compiled cutlass, now I am trying to
compile PyTorch CUDA code with Clang++ compiler.