Date: Fri, 5 May 2017 16:01:06 -0700 From: bob prohaska <fbsd@www.zefox.net> To: Mark Millard <markmi@dsl-only.net> Cc: ports@freebsd.org, freebsd-arm@freebsd.org Subject: Re: RPI2, www/firefox, error: "NEON support not enabled" Message-ID: <20170505230106.GA52464@www.zefox.net> In-Reply-To: <078B736E-4807-42C7-B6A5-656F3A50DAEB@dsl-only.net> References: <20170505151339.GA51255@www.zefox.net> <962F9C0D-C7C8-4940-A381-B3097FD2A138@dsl-only.net> <20170505182838.GB51255@www.zefox.net> <078B736E-4807-42C7-B6A5-656F3A50DAEB@dsl-only.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, May 05, 2017 at 12:38:14PM -0700, Mark Millard wrote: > > An rpi2 has Cortex-A7 (armv7-A) cores that have NEON > but armv6 does not. > > There is some possibility that with something like > -mcpu=cortex-a7 in use as a compiler option that > NEON would be used. What's the simplest way to try it on a self-hosted RPI2 running -current? At this point I'm just using make -DBATCH in /usr/ports/www/firefox and following my nose. There's nothing valuable on the system, it's only for testing. > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217611 > > (VFP and NEON are related by the registers used.) > > So there could be other problems with NEON enabled code > until it is all resolved. (And head gets the work before > stable/11 gets the result.) > Most of the discussion in the thread is beyond me, but it is appreciated that the problem isn't simple. Thanks for writing! bob prohaska
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170505230106.GA52464>