Hi Jakub,
On 2/27/19 10:56 AM, Jakub Jelinek wrote:
On Mon, Feb 25, 2019 at 10:23:52AM +0000, Kyrill Tkachov wrote:
The only bootstraps I'm doing are distro builds with
--with-tune=generic-armv7-a --with-arch=armv7-a \
--with-float=hard --with-fpu=vfpv3-d16 --with-abi=aapcs-linux
I don't have setup nor experience with configuring anything else, don't
really know what is and what isn't ABI compatible etc.
Isn't --with-mode=arm the default with the above set of options? Can
--with-mode=thumb be used ABI compatibly with that, or is that incompatible?
They are ABI-compatible. Running the testsuite with -mthumb in RUNTESTFLAGS
would also be enough in this case if you don't have the cycles for a
bootstrap.
Ok, so tried to do two distro builds with the above plus --with-mode=thumb,
one without the casesi patch, the other one with that.
Both bootstrapped successfully, but dunno why the regtests were too slow to
fit under our hard 2 days timeout limit. When I grabbed the build logs, the
only difference in the grep ^FAIL | sort -u lines was one fewer go failure
with the patch (but that is most likely a random failure rather than the
patch actually changing anything). Is -mthumb generally slower than ARM
mode?
Anyway, I'm afraid this is as far as I can go in my testing.
As discussed on IRC, I've bootstrapped and tested this on
arm-none-linux-gnueabihf.
So from an arm perspective this looks good (but you'll need an aarch64
ok for that component).
Thanks,
Kyrill
Jakub
