|
|
|
|
|
by perturbation
2360 days ago
|
|
Additionally, the Nim code was not compiled with many optimizations turned on! (I.e., without -d:release). $ nim c -o:base64_test_nim -d:danger --cc:gcc --verbosity:0 base64_test.nim
$ nim c -o:json_test_nim -d:danger --cc:gcc --verbosity:0 json_test.nim
IIRC the -d:danger flag is necessary for some optimizations (like disabling bounds checking) but -d:release is necessary for most optimizations to be enabled.Edit: It appears I'm incorrect, -d:danger does imply -d:release in newer Nim versions. |
|