fantastic work.

see the build log https://builds.sr.ht/~ach/job/62505

/home/build/.buildenv: line 10: export: `macos.': not a valid identifier

amazing :D. I wonder how far away you are from building an openbsd kernel :P

Let me know if you find a good CI system for macos. I know zig uses azure pipelines, but I really don't want to set that up ><.

Not even sure if sr.ht will ever support mac.

Those solutions would work - I should perhaps make a bug report to nixos for the wrapper script.

I just did some testing and I can get the unwrapped nixos binutils and the proper dynamic linker path from:

[ac@black:~/src/cc]$ cat $(dirname $(realpath $(which ld)))/../nix-support/orig-bintools
/nix/store/gqq2w8a0yb3ksx9h9iilp73x5hib3rwi-binutils-2.31.1

[ac@black:~/src/cc]$ cat $(dirname $(realpath $(which ld)))/../nix-support/dynamic-linker
/nix/store/sw54ph775lw7b9g4hlfvpx6fmlvdy8qi-glibc-2.27/lib/ld-linux-x86-64.so.2

Probably not necessary for the configure script to be aware of this crap.

I still have two problems with this, on nixos the dynamic linker is not installed at /lib64/ld-linux-x86-64.so.2 , So i need to either detect this, or pass it in somehow.

The related second problem is on nixos, gcc is actually a wrapper script that already specifies --dynamic-linker on it's own, so I get warnings about this flag being passed more than once.

Nixos is a bit of an oddity, so maybe it could have it it's own section in the configure script, however it is not visible from -dumpmachine , as it just appears as x86_64-unknown-linux-gnu.

I know it is a bit of a pain, but I only use nixos, which is why I care about this.

I wonder if it would be helpful to have a script that fetches the correct qbe version and stashes it in a local dir.

I can see an argument for not doing this too, so I'm not sure what is best.

For example, gcc has a script in contrib/ that can download gmp and some other things.

--------------------------------------
TEST:
bug-c45bd91c-b146-4581-adc8-4beec4c70609.c
RESULT:
FAIL
SRC:
void printf();
struct {
  signed a : 6;
} b;
int c;
unsigned char d;
char e;
int main() {
  e = -1;
  d = e;
  c = b.a = d;
  printf("%d\n", c);
}

CC-OUTPUT:
QBE_PATH:
/nix/store/hkn01j1ncivcsvynhb285g9i9vqkqbhb-single-exec/test.qbe
ASSEMBLY_PATH:
/nix/store/hkn01j1ncivcsvynhb285g9i9vqkqbhb-single-exec/test.s
TEST-OUTPUT-DIFF:
--- output.expected     2019-04-25 09:55:31.819073470 +0000
+++ output.actual       2019-04-25 09:55:31.904073452 +0000
@@ -1 +1 @@
--1
+255
EXIT-CODE:
0

No problem - As you said before, the main trick is just having a good 'interesting' function and getting things set up, after that I just have to alt-tab and let csmith do the work.

Here they claim to have a cpp validation suite, it might be nice to test it out when you work on the preprocessor.

http://mcpp.sourceforge.net/