On Mon, 21 Jul 2014, David Wohlferd wrote: > I have been looking at asm_fprintf in final.c, and I think there's a design > flaw. But since the change affects ARM and since I have no access to an ARM > system, I need a second opinion.
There's this thing called cross-compilation, which happens for more than 99% (my guess) of the compiled ARM code distributed in the world - and I believe what most people here do ARM-wise. (Your target system doesn't have to match your host system!) > It would be helpful if someone could confirm that it still > compiles without error under ARM after applying this patch. I'm reluctant to > post this to gcc-patches when it has never been run. Not that the following would constitute the actual testing usually required for a patch, but: /path/to/toplevel/configure --target=arm-eabi && make all-gcc # Yay, the compiler-proper for a "bare iron" ARM compiler. ./gcc/xgcc -B./gcc -S test.c Woot, compiled your first ARM program. :) Just emitting text assembly code, and #include's won't work, but a missing-case leading-to-abort would be prominently noticed as an internal compiler error. The page <https://gcc.gnu.org/simtest-howto.html> is unfortunately out of date (e.g. binutils+sim now lives in the same git repo) but it gives you the idea. Happy hacking. brgds, H-P
