Our great sponsors
- InfluxDB - Collect and Analyze Billions of Data Points in Real Time
- Revelo Payroll - Free Global Payroll designed for tech teams
- SonarCloud - Analyze your C and C++ projects with just one click.
- Onboard AI - Learn any GitHub repo in 59 seconds
-
llvm-project
The LLVM Project is a collection of modular and reusable compiler and toolchain technologies.
The changes are here: https://prereleases.llvm.org/16.0.0/rc3/docs/ReleaseNotes.ht...
Notably, function specialization optimization has been finally enabled by default, although it still seems to only be capable of constant propagating variables of register size [2].
The heuristics are, understandably so, somewhat conservative [2], and I presume there are some projects that could benefit from enabling `-mllvm -funcspec-for-literal-constant`, raising `-mllvm funcspec-max-clones=3` ad lowering `-mllvm -funcspec-min-function-size=100`.
[1] https://godbolt.org/z/jKo7K3jPd
[2] https://github.com/llvm/llvm-project/blob/main/llvm/lib/Tran...
-
Xtensa support (esp32). Will be interesting how this will be for Rust and Zig support for esp32
https://github.com/llvm/llvm-project/tree/main/llvm/lib/Targ...
https://www.phoronix.com/news/LLVM-Xtensa-Backend
https://github.com/espressif/llvm-project/issues/4#issuecomm...
https://github.com/ziglang/zig/issues/5467#issuecomment-1465...
-
InfluxDB
Collect and Analyze Billions of Data Points in Real Time. Manage all types of time series data in a single, purpose-built database. Run at any scale in any environment in the cloud, on-premises, or at the edge.
-
zig
General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
Xtensa support (esp32). Will be interesting how this will be for Rust and Zig support for esp32
https://github.com/llvm/llvm-project/tree/main/llvm/lib/Targ...
https://www.phoronix.com/news/LLVM-Xtensa-Backend
https://github.com/espressif/llvm-project/issues/4#issuecomm...
https://github.com/ziglang/zig/issues/5467#issuecomment-1465...
-
> [...] treated some of the code used for various feature checks invalid and the end result was checks failing even though they should have passed - often with barely any notification to the user (the user would see a "no" instead of a "yes" in some check)
This is a perfect illustration of conceptual bankruptcy of the autoconf approach. Using compile/link tests and basing a decision on whether they succeeded or failed without distinguishing the reasons for failure will inevitably lead to silent false negatives.
If you are wondering what to and what are the alternatives, here is one approach: https://github.com/build2/libbuild2-autoconf
