2026

11

  1. *sshole, or when are we finally going to get rid of C?
  2. Libghostty 1.0
  3. The fastest double-to-string algorithm you’ve never heard of
  4. Switch Lowering in GCC

10musl libc の脆弱性と、メモリ消去の落とし穴

  1. TIL: POSIX wordexp(3) is dangerous
  2. How close can pure functional programming get to C?
  3. CVE-2026-107891: musl libc: multiple integer overflow in regcomp, possibly leading to incorrect allocation sizes and out-of-bounds heap writes
  4. Making all divisions slower to fix a bug in 0.000000000000000000542% of cases
  5. A UAF turned RCE
  6. A modern web app in c
  7. oh, apparently it's not possible to portably check for string-to-float conversion errors in standard c
  8. Zeroization, part 1: Wiping can make things worse
  9. C for Rust Programmers

09標準ライブラリのFMAのバグと、JSからCへ

  1. JavaScriptをC言語にコンパイルする「porffor」がアルファ版に到達。ネイティブやWASMを生成可能
  2. Implementing FMA and finding bugs in C and Rust standard libraries

08Cを置き換える試みと、言語の細部の難しさ

  1. Porffor goes alpha August 11th
  2. Optimizing memory use in a Markdown parser
  3. プログラマーはどの言語からどの言語へ移住しているのか?JetBrainsが8837人分の回答を分析
  4. A faster way to calculate the day-of-the-week
  5. I thought I was building a C replacement. I was wrong
  6. C言語の末尾呼び出し最適化は、実は比較的最近の話
  7. Goに乗っかるという選択
  8. sizeof is surprisingly difficult to parse in C

07

  1. Writing a (valid) C program without main()