Rui Ueyama

Results 604 comments of Rui Ueyama

Confirmed. I have no idea how this behavior can be useful, but this is indeed a bug in chibicc.

As per the C spec, program's behavior is undefined if a struct is empty. So you generally should avoid using it. https://www.sigbus.info/n1570#6.7.2.1p8 That being said, gcc and clang handle empty...

I'd say that the frontend is complete, but as a matter of policy, it doesn't rigorously check for errors. My primary focus was on compiling correct code correctly and everything...

I'll update commit messages, and this should be addressed there. As to robustness, chibicc focuses only on handling correct code correctly and doesn't care too much about incorrect inputs. I...

I'll eventually define `__GNUC__` macro, and I think that should fix this problem. I'm not doing it right now because it opens a can of warms. If you define `__GNUC__`,...

Thank you for your comment. I don't think that I should cover all the details of security enhancement features of compilers, but at least I need to cover what is...

Thanks. I think we should use calloc only when needed. Your patch seems to use calloc even if an allocated memory is initialized immediately.

This is the most significant missing feature as far as I know. We need to calculate an address in the compiler and propagate that information to the codegen. The current...

I'm currently pretty busy creating a new linker from scratch (https://github.com/llvm-mirror/lld/tree/master/COFF), and I also have other things to do. I'll revisit this later.

It really does when you create tens or hundreds of megabytes of executables. It is just too slow. Another problem is that no existing linkers can use multi-cores well. Parallelizing...