For me on the average the code compiles faster.
If you check the change log, these might be some reasons why:
[+] Added SSSE3 (Supplemental SSE3) instructions.
[-] Further optimizations in the parser.
[-] Improved an instruction searching algorithm a bit.
Sure, you won't notice this with a 100-line-code!
If you have large amounts of code you might though.
Or if you rebuild your modules often.
Don't know if the code "itself" runs faster. But when memory leaks are fixed, they might have impact on the runtime speed too?!
Anyway, do as you like. You can always keep a backup of the replaced file.
All the bmx bugs I have found over the past months were not related to the newer compiler!
If you check the change log, these might be some reasons why:
[+] Added SSSE3 (Supplemental SSE3) instructions.
[-] Further optimizations in the parser.
[-] Improved an instruction searching algorithm a bit.
Sure, you won't notice this with a 100-line-code!
If you have large amounts of code you might though.
Or if you rebuild your modules often.
Don't know if the code "itself" runs faster. But when memory leaks are fixed, they might have impact on the runtime speed too?!
Anyway, do as you like. You can always keep a backup of the replaced file.
All the bmx bugs I have found over the past months were not related to the newer compiler!