I've just noticed the armhf target's code generation was actually geared towards v6 for compatibility.
Seeing as you already provide separate armv6 builds it makes sense for the armv7 ones to generate code for v7, incl. at the time of bootstrapping themselves (curiously it's the default on android.)
Literally we're talking about just two commands before the start of the armv7 build:
sed -i s/v6/v7/ src/librustc_back/target/arm_unknown_linux_gnueabihf.rs
and
sed -i s/v6/v7/ mk/cfg/arm-unknown-linux-gnueabihf.mk
To try out the proposed changes anyone can use the scripts from my fork.
I've just noticed the
armhftarget's code generation was actually geared towardsv6for compatibility.Seeing as you already provide separate
armv6builds it makes sense for thearmv7ones to generate code forv7, incl. at the time of bootstrapping themselves (curiously it's the default on android.)Literally we're talking about just two commands before the start of the armv7 build:
sed -i s/v6/v7/ src/librustc_back/target/arm_unknown_linux_gnueabihf.rsand
sed -i s/v6/v7/ mk/cfg/arm-unknown-linux-gnueabihf.mkTo try out the proposed changes anyone can use the scripts from my fork.