f() vs f(void) in C vs C++

TL;DR Prefer f(void) in C to potentially save a 2B instruction per function call when targeting x86_64 as a micro-optimization. -Wstrict-prototypes can help. Doesn’t matter for C++. The ProblemWhile messing around with some C code in godbolt Compiler Explorer, I kept noticing a particular funny case. It seemed with my small test cases that sometimes function calls would zero out the return registe

[rti7743]

コンパイラの最適化時のバグかな・・致命的な問題じゃないから誰も気が付かなかったんだろうな。そのうち治るんでね

[Watson]

ほぅ