pop local variables based on their size

[MaxHearnden]

This caused a program as simple as

struct test {
  int testa;
  int testb;
};

int main() {
  struct test;
  return 0;
}

to fail.

[stikonas]

Looks good, though test checksums will need updating.

Can you update them or should I do it? It is mostly:

• Build mescc-tools and add them to PATH (in particular we need hex2 and M1).
• make clean test

If it doesn't pass, run

• make Generate-test-answers
• sha256sum test/test1000/proof > test/test1000/proof.answer
• make clean test

[oriansj]

We don't push variables on the stack based on size; so popping variables on the stack will result in an unbalanced stack.

So you'll have to make our pushes onto the stack match the variable size (rather than fixed to register size) if you want this behavior in M2-Planet

[MaxHearnden]

It already does https://github.com/oriansj/M2-Planet/blob/master/cc_core.c#L2051-L2064

[MaxHearnden]

I've rebased (in case there are any significant code base changes) and updated the test answers

[stikonas]

I've rebased (in case there are any significant code base changes) and updated the test answers

Thanks, I'll test this tomorrow.

[stikonas]

@MaxHearnden were you actually able to compile that test program at any point.

Now I'm getting a.c:7:struct 'test' already has definition. but even if I rebase you commit on older M2-Planet, I still get different error: forbidden character in local variable name.