From owner-freebsd-arm@freebsd.org Thu Mar 16 16:14:11 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0DDEAD0F690 for ; Thu, 16 Mar 2017 16:14:11 +0000 (UTC) (envelope-from sylvain@sylvaingarrigues.com) Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 98B811AA4 for ; Thu, 16 Mar 2017 16:14:10 +0000 (UTC) (envelope-from sylvain@sylvaingarrigues.com) Received: by mail-wm0-x229.google.com with SMTP id u132so39324302wmg.0 for ; Thu, 16 Mar 2017 09:14:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sylvaingarrigues-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=jeHFzViCg/8rZI5L2rVdtBXClfNTAXC/M4w0ww46ef0=; b=Nam/FgSGBa/Kuis3o5M3fTYEEgcSibGkOKUdw2eUIw+qnfC31/qW3E70tmHdyFmspM B7R7zgzNStqT9i2zcMRsEuok8jO80XANF7GUTwx2F0CW7ZYaCE7rYWBE4h/blSk6dw+e DcqgPI4gqLRVST6eJGXINyDHvltvA5K9HK47cevI7ulMKxvygr7PVUdMIi6vxw2gB02O pNUA/wyf/gcXKNI2fgvURytdcxeGAt4xSuXtNML4bsjrhDFwNEOfRmxNMxJ2VvVLRFCR TrfEBXeaAi/XkZDEyuugkzCADB63rhyM5tVxHwu+vwXrGhbOgqCCAPzZ6iMQfM1gGLkl XOWA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=jeHFzViCg/8rZI5L2rVdtBXClfNTAXC/M4w0ww46ef0=; b=Ju0AISs7U679MIHHdbmwdBSEChqqKgkX6A1ilq8SvwmFrGwiQAbreWBYjYkziRI/vf pjMtpIO/lvT8I0SaBTW1KLrRtuDakGhgnbf322dZVMUzEF8Ank/nWyazEJPNMrgHg5sB 78kgtmed771KH8Ye8gQgL5yaycY0i1dm7wnjFHt+shvVC7Rvoy96pZnZGuzdwGsPHr1z aTgsf5TZqTgr9+HQy93aHFxRxI3XXxMCE0qBfcZA0CY84d2/+ZiPyO/7m/6jQFGnh0vt bmH9zHclRW2LFnZl4P9ejs0XzYKWrn20l0kKFAF7QoWS8T1PQkMMa94hMuvj2cRbzUXW Thww== X-Gm-Message-State: AFeK/H2GC0EKMKn6zwr47dUaWt1pmqGk8lUNqlRf6+aIZ6BzZecNhH9uSb4qtYq5Dh9pvA== X-Received: by 10.28.11.69 with SMTP id 66mr27382786wml.38.1489680848724; Thu, 16 Mar 2017 09:14:08 -0700 (PDT) Received: from [172.21.11.111] ([158.255.96.238]) by smtp.gmail.com with ESMTPSA id h3sm6728837wrb.6.2017.03.16.09.14.07 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 16 Mar 2017 09:14:07 -0700 (PDT) From: Sylvain Garrigues Message-Id: Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: Is CPUTYPE=cortex-A7 supposed to work? Date: Thu, 16 Mar 2017 17:14:06 +0100 In-Reply-To: <674facba-68cd-8ce1-887a-1ef3c51520bc@freebsd.org> Cc: freebsd-arm To: mmel@freebsd.org References: <871suc3nv8.fsf@news-spur.riddles.org.uk> <8737ely05c.fsf@news-spur.riddles.org.uk> <87wpbxw3yd.fsf@news-spur.riddles.org.uk> <79EBD44B-2C2D-4394-A90C-DF494A049F20@dsl-only.net> <674facba-68cd-8ce1-887a-1ef3c51520bc@freebsd.org> X-Mailer: Apple Mail (2.3259) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Mar 2017 16:14:11 -0000 > Le 16 mars 2017 =C3=A0 16:16, Michal Meloun 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=