Code like

const int kBitsPerByte = 8;                        // bits
const int kWordSize = sizeof(word);                // bytes
const int kBitsPerWord = kWordSize * kBitsPerByte; // bits

is not valid C because kWordSize * kBitsPerByte is not a constant expression in C. This works with with Clang because it's more permissive but not in GCC. Investigate & fix.

Thank you for your great post on DDCG! Reading your implementation of the register stack reminded me that I saw the same trick at rubyconf in 2021, in this talk: https://www.youtube.com/watch?v=4vDfegrjUtQ. It might be worth adding a link to it as well, incrementally working towards the original source of that technique :)

https://johnpaton.net/posts/console-highlighting/

The domain is missing GitHub Pages' AAAA records for IPv6 support, which are:

2606:50c0:8000::153
2606:50c0:8001::153
2606:50c0:8002::153
2606:50c0:8003::153 

Everyone keeps asking

Regarding the post https://bernsteinbear.com//blog/compiling-ml-models/ , I'm curious how the Zig compiler of C code will contrast with Clang and TCC.

Cast to unsigned char

Hi, this is an excellent post. If I was aware that you could harness the REPL, I certainly didn't recall it.
I started thinking of how I'd customize your code from your article and ran into the fact
that for all the use cases that I can think of, I'd just use the BPython REPL, which is really, really, nice.
It seems you can even embed BPython in a program:
https://snyk.io/advisor/python/bpython/functions/bpython.embed

I think it's worth you adding a line or two to talk about when your technique would be the best thing,
and mentioning both BPython and IPython as ready-to-go alternatives for situations where that
would work. I use BPython for quickly trying things all the time.

My best,
Eirikur

I was reading your post regarding gen.py and generator for c code. You mentioned a java builder for a sea of nodes project. Do you have the code on github?

I'm quite confused about this header. Should we just "use" it, as is? If that is the case then perhaps a link to the file would be OK.

Also, when I compare the definition of the macro EXPECT_EQUAL_BYTES in page vs in github:
page:

#define EXPECT_EQUALS_BYTES(buf, arr) ASSERT_MEM_EQ(arr, (buf)->address, sizeof arr)

git:

#define EXPECT_EQUALS_BYTES(buf, arr) Testing_expect_buffer_equals_bytes((buf), (arr), sizeof arr)

Is this important? I can't get it to compile with gcc -Wall -Wextra -pedantic -fno-strict-aliasing