yagarto

Yagarto (GCC, Win32) compiles same code differently on different PCs

有些话、适合烂在心里 提交于 2019-12-06 08:33:42
问题 I am using a Yagarto toolchain on Windows to compile a codebase of about 100K lines of code. We have two development PCs. However, they each build slightly different binaries despite having the same toolchain and building the same source code. I have checked using MD5 that we have the same compiler binaries, the same system headers, and we are compiling the same source, with the same commandline being passed to GCC, yet there are subtle differences. Out of the 81 object files in our codebase,

Yagarto (GCC, Win32) compiles same code differently on different PCs

萝らか妹 提交于 2019-12-04 13:13:40
I am using a Yagarto toolchain on Windows to compile a codebase of about 100K lines of code. We have two development PCs. However, they each build slightly different binaries despite having the same toolchain and building the same source code. I have checked using MD5 that we have the same compiler binaries, the same system headers, and we are compiling the same source, with the same commandline being passed to GCC, yet there are subtle differences. Out of the 81 object files in our codebase, 77 compile exactly the same; and four have minor differences. There is no functional difference, but

What is the rationale behind removing crt0.o from gcc4.7.x?

吃可爱长大的小学妹 提交于 2019-12-01 17:05:12
问题 I am trying to upgrade to yagarto4.7.2 (Yet Another GNU ARM toolchain, for those wondering), which is gcc and binutils, ported for Windows. However, trying to compile a simple Hello World yields: c:/yagarto-20121222/bin/../lib/gcc/arm-none-eabi/4.7.2/../../../../arm-none-eabi /bin/ld.exe: cannot find crt0.o: No such file or directory collect2.exe: error: ld returned 1 exit status Now, in this forum it is made clear that this is the startup initialziation library, that was removed after gcc4.6