• State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 24 subscribers
  • Views 6245 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

GNU ARM Embedded Toolchain takes more time to compile on Windows 10 than Windows 7

anudhi

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.exe
2) arm-none-eabi-as.exe
3) arm-none-eabi-ld.exe

It 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.

Parents
  • 0

    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)

Reply
  • 0

    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)

Children
No data