This query is regarding the time difference the GNU ARM Embedded Toolchain takes to build a system on Windows 10 vs Windows 7.Earlier I was using Windows 7 for compilation of a large bare metal system(around 5000 files) and it took around 2.5 hours to complete the build.Now, I migrated to Windows 10 and it takes around 12 hours to complete the same build.Executables used:1) arm-none-eabi-gcc.exe2) arm-none-eabi-as.exe3) arm-none-eabi-ld.exeIt would be really great if you could direct me in the right direction to resolve this issue and if there's anyway to reduce the build time.
Could you possibly reduce this down to the files in the compilation that takes the longest? It would be good to find a test case that is representative of the delay in compilation. You could append a time to the compilation command line in your make file where you invoke the compiler (eg. CC = 'time arm-none-eabi-gcc'). You could then parse and compare the logs on Windows 10 and 7. More info will be helpful eg are you doing the build under a cygwin environment? Cygwin usually adds another layer to the execution.
I have found anti virus software that scans an executable every time it is run will make my builds about 5 times longer. You seem to be right at that mark so that would be my guess. Either stop the Anti Virus or make if not scan "arm-none-eabi-gcc.exe" each and every time it is invoked. (I don't seem any issue between Windows 7 and Windows 7 for build times)
Is this on different computers, or is it the same computer that's been updated (sic?) from Win-7 to 10 ?
If different computers, are the Win-7 and Win-10 machines otherwise identical?
Have other applications similarly slowed?
View all questions in GNU Toolchain forum