On Fri, Feb 22, 2019 at 11:02:11PM +0100, Uwe Kleine-König wrote: > On 2/20/19 10:12 PM, Luc Van Oostenryck wrote: > > On Wed, Feb 20, 2019 at 05:17:29PM +0100, Uwe Kleine-König wrote: > >> On 2/20/19 12:25 PM, Luc Van Oostenryck wrote: > >>> > >>> I still consider it more or less as RFC since it's lack some testing. > >>> And since it started from Uwe's patch for Debian builds, I would > >>> prefer to hear his opinion about it first. > >> > >> Do you have this in a branch somewhere to pull? Then I can give it a go > >> on a few Debian porter machines. > > > > That would be wonderful. I've put the branch at: > > git://git.kernel.org/pub/scm/devel/sparse/sparse-dev.git cgcc-dumpmachine-v2 > > > > It's the same as the patches posted here but: > > *) with the last 2 patches removed > > *) with Ramsay's comments taken in account > > *) rebased on top of the current master. > > I gave this branch a go in a mips chroot on a mips64 machine and > > env CHECK=./sparse ./cgcc -no-compile memops.c > > was happy there. Ditto on an armhf chroot on arm64. The change I made for ARM's -mfloat-abi was buggy but at least this show that the logic for the arch selection is good. Thanks a lot, -- Luc
