From owner-freebsd-arm@freebsd.org Tue Apr 2 20:36:49 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E7FBC1572EA7; Tue, 2 Apr 2019 20:36:48 +0000 (UTC) (envelope-from jfc@mit.edu) Received: from outgoing-exchange-1.mit.edu (outgoing-exchange-1.mit.edu [18.9.28.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.outgoing-exchange.mit.edu", Issuer "InCommon RSA Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 62B9677277; Tue, 2 Apr 2019 20:36:47 +0000 (UTC) (envelope-from jfc@mit.edu) Received: from oc11exedge2.exchange.mit.edu (OC11EXEDGE2.EXCHANGE.MIT.EDU [18.9.3.18]) by outgoing-exchange-1.mit.edu (8.14.7/8.12.4) with ESMTP id x32KVDvb016837; Tue, 2 Apr 2019 16:31:15 -0400 Received: from W92EXHUB15.exchange.mit.edu (18.7.73.26) by oc11exedge2.exchange.mit.edu (18.9.3.18) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Tue, 2 Apr 2019 16:31:01 -0400 Received: from OC11EXPO24.exchange.mit.edu ([169.254.1.112]) by W92EXHUB15.exchange.mit.edu ([18.7.73.26]) with mapi id 14.03.0439.000; Tue, 2 Apr 2019 16:31:12 -0400 From: John F Carr To: bob prohaska CC: "freebsd-arm@freebsd.org" , "freebsd-ports@freebsd.org" Subject: Re: RPI3, error: invalid operand in inline asm: 'rev16 ${0:w}, ${1:w}' Thread-Topic: RPI3, error: invalid operand in inline asm: 'rev16 ${0:w}, ${1:w}' Thread-Index: AQHU5wysVg2BgjPU/Ui4D1u3G3LuWKYktxyAgAOtYgCAAJE5AIAAXk2AgAAfRoCAACevgA== Date: Tue, 2 Apr 2019 20:31:12 +0000 Message-ID: References: <20190330152327.GA11933@www.zefox.net> <236A3D25-0B4D-46DA-95BA-71DA505CC2E0@exchange.mit.edu> <20190402015956.GA27268@www.zefox.net> <28F4BF7B-4391-4A4B-ABEC-36A154F9FAE2@exchange.mit.edu> <20190402161713.GA30854@www.zefox.net> <20190402180909.GA31620@www.zefox.net> In-Reply-To: <20190402180909.GA31620@www.zefox.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [18.9.1.84] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Rspamd-Queue-Id: 62B9677277 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of jfc@mit.edu designates 18.9.28.15 as permitted sender) smtp.mailfrom=jfc@mit.edu X-Spamd-Result: default: False [-1.25 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; HAS_XOIP(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip4:18.9.28.0/24]; NEURAL_HAM_LONG(-0.92)[-0.916,0]; MIME_GOOD(-0.10)[text/plain]; SUBJECT_HAS_CURRENCY(1.00)[]; DMARC_NA(0.00)[mit.edu]; TO_DN_SOME(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: mit-edu.mail.protection.outlook.com]; NEURAL_HAM_SHORT(-0.29)[-0.286,0]; NEURAL_HAM_MEDIUM(-0.73)[-0.726,0]; IP_SCORE(-0.01)[asn: 3(-0.00), country: US(-0.06)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:3, ipnet:18.9.0.0/16, country:US]; RCVD_TLS_LAST(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Apr 2019 20:36:49 -0000 >=20 > On Apr 2, 2019, at 14:09 , bob prohaska wrote: >=20 > On Tue, Apr 02, 2019 at 09:17:13AM -0700, bob prohaska wrote: >> On Tue, Apr 02, 2019 at 10:39:42AM +0000, John F Carr wrote: >>>=20 >>> The problem I mentioned is with the system. I filed a bug: >>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D236920 >>>=20 >>> If you change the system header /usr/include/machine/endian.h >>> according to the path in that bug report, does chromium compile? >>=20 >> The patch applied without difficulty and I've restarted the make >> process using portmaster-devel.=20 >>=20 >=20 > The compile stopped again, seemingly with the same error, unchanged. >=20 > Oddly, there's also an error immediately before, which has been seen > before but I thought has been fixed at some point,=20 >=20 > In file included from ../../base/third_party/libevent/event.c:49: > In file included from /usr/include/signal.h:42: > /usr/include/machine/ucontext.h:46:2: error: unknown type name '__uint128= _t' > __uint128_t fp_q[32]; > ^ > 1 error generated. >=20 > The relevant parts of the console output are at >=20 > http://www.zefox.net/~fbsd/rpi3/portmaster/chromium/r345516/console.txt >=20 > in case anybody's willing to take a look. >=20 > Thanks for reading, >=20 > bob prohaska I looked a little closer and figured out why it's failing. The chromium po= rt compiles with options "--target=3Darm-linux-gnueabihf -march=3Darmv7-a".= That means it's using a Linux ABI on 32 bit ARM v7. The byte reverse fun= ctions in machine/endian.h do not work with that target. I think the rev* = instructions don't exist in ARM v7. Does chromium come with object files built for ARM7a on Linux, so that targ= et has to be used?=