Yes, and for me it is:
$ nim c -r t.nim
Hint: used config file '/home/stefan/Nim/config/nim.cfg' [Conf]
Hint: system [Processing]
Hint: t [Processing]
CC: t
CC: stdlib_system
Hint: [Link]
Hint: operation successful (11719 lines compiled; 0.667 sec total;
22.539MiB peakmem; Debug Build) [SuccessX]
Hint: /tmp/hhh/t [Exec]
94177739211386
stefan@nuc /tmp/hhh $ ./t
94314291364474
stefan@nuc /tmp/hhh $ ./t
94655466492538
stefan@nuc /tmp/hhh $ nim -v
Nim Compiler Version 0.18.0 [Linux: amd64]
Copyright (c) 2006-2018 by Andreas Rumpf
git hash: 4164ec4f8b6d9968e69381edd35d9cf6fe79dee1
active boot switches: -d:release
You may inspect the C code to see that var is not initialized. dd var is
located on the stack and may be zero if never another value was written to this
location. You may try to call another proc which writes some values to local
variables, that should pollute the stack. And then call your ff proc.
