Date: Thu, 16 Mar 2017 17:14:06 +0100 From: Sylvain Garrigues <sylvain@sylvaingarrigues.com> To: mmel@freebsd.org Cc: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: Is CPUTYPE=cortex-A7 supposed to work? Message-ID: <ED8405B6-1150-4A9C-AD93-5C74306FB361@sylvaingarrigues.com> In-Reply-To: <674facba-68cd-8ce1-887a-1ef3c51520bc@freebsd.org> References: <871suc3nv8.fsf@news-spur.riddles.org.uk> <CANCZdfq4EwH%2B_9FVNai8s6Y-gdTjHJ8dNkJwSrnF%2BSAkdwvYdg@mail.gmail.com> <8737ely05c.fsf@news-spur.riddles.org.uk> <CANCZdfpftVHaPahTOP0vxB-FR%2BKtpqY9JMJr=F2DGifD0fhKMQ@mail.gmail.com> <87wpbxw3yd.fsf@news-spur.riddles.org.uk> <79EBD44B-2C2D-4394-A90C-DF494A049F20@dsl-only.net> <E6BC9F77-F65B-4918-9E22-3BFECA268E30@sylvaingarrigues.com> <674facba-68cd-8ce1-887a-1ef3c51520bc@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> Le 16 mars 2017 =C3=A0 16:16, Michal Meloun <melounmichal@gmail.com> a = =C3=A9crit : >=20 > Firstly, thanks to Andrew for perfect bug analysis. > Currently, you can compile you kernel/userland/port with = CPUTYPE/CFLAGS > without any additional problem(s). I use this for all my ARM systems = for > more that last 6-months... >=20 > The 'other' interfaces are gdb, porcfs, libpthtread. I work on this, = but > I still have not any output. Thank you so much for your quick feedback Michal. Good to know this = matter is into good hands. I=E2=80=99m afraid I'm still afraid about = `basic=E2=80=99 programs like git being still potentially broken when = kernel+world+ports have CPUTYPE=3Dcortex-a7 in make.conf - Andrew said a = simple `git clone' could fail, more precisely (quoting him): > I have determined that the sha1 failures occur only if the = NEON-enabled > SHA1 block function is interrupted by a signal. This explains why it > fails in git (which is using SIGALRM to set a "display progress" flag) > but not in standalone SHA1 tests; Removing CPUTYPE apparently fixes things hence I=E2=80=99m not 100% = confident yet of keeping CPUTYPE=3Dcortex-a7 myself even if only a few = ports might be affected. Git is an important port, who knows what other = ports are broken :-) Are you also working on the kernel part (as part of = the =E2=80=98other interfaces=E2=80=99 you mentioned) to fix this = fp-register-preserving-during-signal?=20 Thanks one more time for all analyses done so far and thanks in advance = for future work on this matter :-) Cheers=20=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ED8405B6-1150-4A9C-AD93-5C74306FB361>