!!!

[beryll1um]

learn C++ first so you don't have to write like that. A shame!!!

Linked: https://github.com/APoCpp/QMLTemplate/issues/1

[melonges]

learn C++ first so you don't have to write like that. A shame!!!

Linked: https://github.com/APoCpp/QMLTemplate/issues/1

[beryll1um]

To teach you not to clog the issues of other projects, perhaps I'll give real important comments:

Using printf in cases where you don't need to format string - bad practice
https://github.com/mellonges/terminal-fps-checker/blob/ef0fc0da27fb02fba90e091b6fd04b321786a4c5/main.c#L27
https://github.com/mellonges/terminal-fps-checker/blob/ef0fc0da27fb02fba90e091b6fd04b321786a4c5/main.c#L33
https://github.com/mellonges/terminal-fps-checker/blob/ef0fc0da27fb02fba90e091b6fd04b321786a4c5/main.c#L35
https://github.com/mellonges/terminal-fps-checker/blob/ef0fc0da27fb02fba90e091b6fd04b321786a4c5/main.c#L49
https://github.com/mellonges/terminal-fps-checker/blob/ef0fc0da27fb02fba90e091b6fd04b321786a4c5/main.c#L50

Compiler doesn't optimizing printf in puts, if the last printable is not
'\n'. You must use fputs.

Please check:

gcc -O3 main.c
objdump -M x86-64 -j .text -d a.out

You mentioned that you are a performance optimization engineer at Intel, but such mistakes are a shame for you as a specialist.

[melonges]

Я исправил на fputs и результат тот же

[beryll1um]

main.1.c.txt
objdump.1.txt
main.2.c.txt
objdump.2.txt

Please look around 144 line in objdump output files =)

gcc -O3 main.c
objdump -M x86-64 -j .text -d a.out