What processors is piCore compiled for?

[gadget42]

the whole world is a supermarket tabloid - unknown

[Paul_123]

It’s obvious that person has no idea what they are doing.  It’s always necessary to need that stuff when cross compiling.

[gadget42]

It’s obvious that person has no idea what they are doing.  It’s always necessary to need that stuff when cross compiling.

to clarify, she said "So, I went and did a build on the B+ natively. It also broke."

are you saying that that is cross-compiling?

[Paul_123]

If the compiler was not built on armv6, then it’s always a problem.

[Paul_123]

Perhaps I was being too sensational in my response too.   But to elaborate.   I doubt there is a single distribution keeping separate repositories for every processor.  Even piCore, where we have an armv6, armv7, armv7l the code in those repositories is not natively compiled.  Also in piCore's case gcc is built on an armv7l processor gcc is configured by the maintainer to produce code compiled for armv6, and for the most part will do that for the casual user who builds code like

gcc -o foo foo.c

It is true that Clang/LLVM is much more restrictive in the code that it produces by default.   But it has been that way, and you should always specify the desired target.  If you download some source for a programs distribution, almost all of them use some sort of configure system (autoconf/libtool, meson, etc)  The job of the configure system is to determine the host compiler and the target. Which then tells gcc/clang specifically what to do.

[gadget42]

reminded of Bruce Schneier's 2006 post and referencing David A. Wheeler regarding trusting-trust and compiling-compilers

for reader convenience:
Mr. Schneier:
https://www.schneier.com/blog/archives/2006/01/countering_trus.html
Mr. Wheeler:
https://dwheeler.com/trusting-trust/

thought-provoking nevertheless

@Paul_123
as always, thank you and kudos for your considerations and thoughts!

20231201-0914am-cdt-usa-modified: originally forgot to add @Paul_123 comment