Closed ingenieroariel closed 1 year ago
Building cosmo under blink on x86 produces a lot of interesting gcc errors too. I'm going to look into this. It's possible there's some kind of opcode bug.
So far the minimum steps to reproduce are:
cc1
binary// reproduce no. 1
struct hi {
int there : 1;
};
// reproduce no. 2
unsigned long strtoul(const char *, char **, int)
__attribute__((__nonnull__(1)));
Under Blink, GCC 9.2.0 (specifically) reads the 1's above as 0. Then prints errors accordingly.
I'm currently building GCC 9.2.0 with more debug symbols to see if I can narrow down where things are going wrong.
Blink version:
Steps done to trigger the problem: