#3073 block-scope static const uninitialized

[Philipp Klaus Krause]

block-scope static const objects don't get initialized, e.g.

int f(void)
{
  static const int a;
  static const int b;
  return a + b;
}

Might return something other than 0. However, both a and b are static, and should thus get implicitly initalized to 0 at program startup (see 6.7.9p10 in the C2X draft N2479 - AFAIK the same holds in all earlier C standards).

This can easily be reproduced by removing the #if 0 in bug-3040.c regression test.

[Philipp Klaus Krause]

From the asm code, it looks as if space for these is allocated, as for initalized const variables, but no value is there, i.e. we see just something like

_f_a_65536_8:
    .ds 1

to be placed somewhere in read-only memory.

[Philipp Klaus Krause]

This also affects other const objects that should be default-initialized, and still happens in SDCC from current trunk:

const int a;
static const int b;

int f(void)
{
  static const int a;
  static const int b;
  return a + b;
}

[Philipp Klaus Krause]

Fixed in [r13674].