--debug is faster to run than non debug.

[onehundredfeet]

I'm finding a very odd behaviour where I'm finding the same code with --debug is running about 1/6th (approx 15%) faster than without. This is the opposite of what I would expect.

I've tried both hashlink and hl/c. I have no idea why --debug would be faster. This is the only switch I am changing.

Any ideas? I'm happy investigating, but it seems to be broadly distributed across all routines, rather than a single routine taking longer.

[ncannasse]

That's very weird as --debug shouldn't change much HashLink output. You can compare the dump/hlcode.txt with -D dump Le sam. 16 mars 2024 à 14:45, Ryan Cleven ***@***.***> a écrit :

…

I'm finding a very odd behaviour where I'm finding the same code with --debug is running about 1/6th (approx 15%) faster than without. This is the opposite of what I would expect. I've tried both hashlink and hl/c. I have no idea why --debug would be faster. This is the only switch I am changing. Any ideas? I'm happy investigating, but it seems to be broadly distributed across all routines, rather than a single routine taking longer. — Reply to this email directly, view it on GitHub <#662>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHZXQBFJJUR5PFIX247L4TYYS4OLAVCNFSM6AAAAABEZT44KGVHI2DSMVQWIX3LMV43ASLTON2WKOZSGE4TAMRWG44TCNY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[ncannasse]

You can compare bytecode output with -D dump=pretty then look at dump/hlcode.txt