Date: Thu, 11 May 2017 19:16:07 -0700 From: Mark Millard <markmi@dsl-only.net> To: bob prohaska <fbsd@www.zefox.net> Cc: ports@freebsd.org, freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: www/firefox on RPI2: error: instruction requires: armv6t2 Message-ID: <85B88765-A708-414B-A465-14A044196D3D@dsl-only.net> In-Reply-To: <20170512014441.GA77264@www.zefox.net> References: <CAJwjRmR8NswYgkM6RjT5vi_OR63eaXCphV7_RToEnXzZqQKcWA@mail.gmail.com> <20170508233241.GA65262@www.zefox.net> <CAJwjRmSxxpNX44T1Aqrg8VWceP4zL1BO5s33RZX8VGiWYo=dnQ@mail.gmail.com> <20170509230236.GA69546@www.zefox.net> <CAJwjRmQiON9J8zZyb7ad5YNo7Ccrdwd0W%2B-6rqzwdcZp%2BEXv%2Bw@mail.gmail.com> <20170510151019.GA70628@www.zefox.net> <CAJwjRmTuXTcG2%2Bxm4tEwV6NRec9Y_kP62_Zza1=YQq508d0fFQ@mail.gmail.com> <20170511033754.GA74153@www.zefox.net> <3C56C526-24E4-45D4-B202-562BD7CB22C2@dsl-only.net> <80B1CCCF-A151-40B8-87D5-CADD513CFAAD@dsl-only.net> <20170512014441.GA77264@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2017-May-11, at 6:44 PM, bob prohaska <fbsd at www.zefox.net> wrote: > On Thu, May 11, 2017 at 01:53:33PM -0700, Mark Millard wrote: >>=20 >> It would help others help you if the assembler or >> compiler command that specifically generated this >> error message was also included in the text that >> you quote. Then we could see what the command >> was and what options had been supplied to it >> (and so what had not been supplied as well). >>=20 > If someone can tell me how to capture that information I'll gladly do = it;=20 > at this stage I do not know how. >=20 > The files referenced in the error message have been placed at > http://www.zefox.net/~fbsd/rpi2/firefox/assembler_failure/ > along with a transcript of stdout/stderr in make.log The (long) line for processing filter_ar_fast_q12_armv7.S was about 19 lines back from the first filter_ar_fast_q12_armv7.S error message in that make.log: (copy/paste may have split the line into multiple below) /usr/bin/cc -std=3Dgnu99 -o filter_ar_fast_q12_armv7.o -DNDEBUG = -DTRIMMED=3D1 -D_FILE_OFFSET_BITS=3D64 -DCHROMIUM_BUILD = -DUSE_LIBJPEG_TURBO=3D1 -DUSE_NSS=3D1 -DGTK_DISABLE_SINGLE_INCLUDES=3D1 = -DENABLE_REMOTING=3D1 -DENABLE_WEBRTC=3D1 -DENABLE_CONFIGURATION_POLICY = -DENABLE_INPUT_SPEECH -DENABLE_NOTIFICATIONS -DENABLE_GPU=3D1 = -DENABLE_EGLIMAGE=3D1 -DUSE_SKIA=3D1 -DENABLE_TASK_MANAGER=3D1 = -DENABLE_WEB_INTENTS=3D1 -DENABLE_EXTENSIONS=3D1 = -DENABLE_PLUGIN_INSTALLATION=3D1 -DENABLE_PROTECTOR_SERVICE=3D1 = -DENABLE_SESSION_SERVICE=3D1 -DENABLE_THEMES=3D1 -DENABLE_BACKGROUND=3D1 = -DENABLE_AUTOMATION=3D1 -DENABLE_PRINTING=3D1 = -DENABLE_CAPTIVE_PORTAL_DETECTION=3D1 -DWEBRTC_RESTRICT_LOGGING = -DWEBRTC_MOZILLA_BUILD -DEXPAT_RELATIVE_PATH -DWEBRTC_ARCH_ARM = -DWEBRTC_ARCH_ARM_V7 -DWEBRTC_BUILD_NEON_LIBS -DWEBRTC_DETECT_NEON = -DWEBRTC_BSD -DWEBRTC_THREAD_RR -DWEBRTC_POSIX = -DWEBRTC_INCLUDE_INTERNAL_AUDIO_DEVICE -D__STDC_FORMAT_MACROS = -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=3D0 -DSTATIC_EXPORTABLE_JS_API = -DMOZ_HAS_MOZGLUE -DMOZILLA_INTERNAL_API -DIMPL_LIBXUL -fPIC = -Wa,--noexecstack -include = /usr/ports/www/firefox/work/firefox-53.0.2/obj-armv6-unknown-freebsd12.0/m= ozilla-config.h -DMOZILLA_CLIENT = -I/usr/ports/www/firefox/work/firefox-53.0.2/media/webrtc/trunk = -I/usr/ports/www/firefox/work/firefox-53.0.2/media/webrtc/trunk/webrtc/com= mon_audio/resampler/include = -I/usr/ports/www/firefox/work/firefox-53.0.2/media/webrtc/trunk/webrtc/com= mon_audio/signal_processing/include = -I/usr/ports/www/firefox/work/firefox-53.0.2/obj-armv6-unknown-freebsd12.0= /ipc/ipdl/_ipdlheaders = -I/usr/ports/www/firefox/work/firefox-53.0.2/ipc/chromium/src = -I/usr/ports/www/firefox/work/firefox-53.0.2/ipc/glue -c = /usr/ports/www/firefox/work/firefox-53.0.2/media/webrtc/trunk/webrtc/commo= n_audio/signal_processing/filter_ar_fast_q12_armv7.S As I guessed the string "-mcpu=3Dcortex-a7" does not appear in the command. But it does indicate that /usr/bin/cc is being used to get to the assembler --which I did not guess. If I guessed right about part of the rule.mk that processed the .S file then the implication would be that: AS=3D/usr/bin/cc So it might be that having ASFLAGS contain -mcpu=3Dcortex-a7 might propagate through to the underlying assembler processing in a way to allow the sbfx instructions by telling it the type of cpu to target. =3D=3D=3D Mark Millard markmi at dsl-only.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?85B88765-A708-414B-A465-14A044196D3D>