andrewchambers

@QuestionPython Your bug is for my C compiler, this is the wrong repository.

it needs to be bootstrapped with an existing compiler, once that is done you can use 8cc to compile 8cc and can forget about the existing compiler. that is what...

Read the README, the project deliberately ignores memory issues. edit: HACKING.md

The backend for 8cc is not too complicated, though @rui314 doesn't seem to be maintaining this project actively at the moment.

It would be far less work to just add C11 to the libfirm c frontend.

To be honest, I wish travis didn't require code to be in the repo to work, in general I feel like the code will outlive the travis ci company.

It is handy to have a sensible default for most values. If this was going to be added, It would be better style to create a wrapper around malloc which...

relevant documentation: C11 6.6 Constant expressions: "10 An implementation may accept other forms of constant expressions" - ugh, I guess we just need to accept whatever gcc accepts.

It is a really tough problem, Here are some crazy examples: ``` // Works fine on gcc. int *x = &(int[]){1, 2 ,3}[1]; // Fails on gcc, not constant, even...

commit 3e0527427850651b1dc385883de519812946622d adds some progress to this.