From owner-freebsd-ppc@freebsd.org Sun Jan 10 09:52:45 2016 Return-Path: Delivered-To: freebsd-ppc@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 75CDDA6951E for ; Sun, 10 Jan 2016 09:52:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 667CB1A43 for ; Sun, 10 Jan 2016 09:52:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u0A9qjSK058817 for ; Sun, 10 Jan 2016 09:52:45 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ppc@FreeBSD.org Subject: [Bug 205440] lang/gcc49, lang/gcc5, devel/powerpc64-gcc on powerpc64: binds a.out to /libexec/ld-elf32.so.1 instead of /libexec/ld-elf.so.1 Date: Sun, 10 Jan 2016 09:52:45 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: markmi@dsl-only.net X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: andreast@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Jan 2016 09:52:45 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D205440 --- Comment #3 from Mark Millard --- devel/powerpc64-gcc that I had listed in the submittal was not updated. Updating /usr/ports to -r405653 and rerunning portmaster -DK devel/powerpc64-gcc still ends up with (found via find . . . -exec grep . .= . -print): #define FREEBSD_DYNAMIC_LINKER32 "/libexec/ld-elf32.so.1" #define FREEBSD_DYNAMIC_LINKER64 "/libexec/ld-elf.so.1" /usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/gcc-5.2.0/gcc/config/= rs6000/freebsd64.h I'm not sure if Bug 205440 should be "unclosed" or if a new bug should be submitted: lang/gcc49 and lang/gcc5 seem to have been updated just fine by their recent updates. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-ppc@freebsd.org Sun Jan 10 09:55:52 2016 Return-Path: Delivered-To: freebsd-ppc@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 E4E07A69632 for ; Sun, 10 Jan 2016 09:55:52 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CDBD21AB2 for ; Sun, 10 Jan 2016 09:55:52 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u0A9tq5C062923 for ; Sun, 10 Jan 2016 09:55:52 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ppc@FreeBSD.org Subject: [Bug 205394] lang/gcc49, lang/gcc5, devel/powerpc64-gcc on powerpc64: lib32's libedit fails to compile, 10 line source shows the problem Date: Sun, 10 Jan 2016 09:55:52 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: markmi@dsl-only.net X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: andreast@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Jan 2016 09:55:53 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D205394 --- Comment #3 from Mark Millard --- devel/powerpc64-gcc that I had listed in the submittal was not updated. Updating /usr/ports to -r405653 and rerunning portmaster -DK devel/powerpc64-gcc still ends up with (found via find . . . -exec grep . .= . -print): #undef WCHAR_TYPE #define WCHAR_TYPE (TARGET_64BIT ? "int" : "long int") #undef WCHAR_TYPE_SIZE #define WCHAR_TYPE_SIZE 32 /usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/gcc-5.2.0/gcc/config/= rs6000/freebsd64.h I'm not sure if Bug 205394 should be "unclosed" or if a new bug should be submitted: lang/gcc49 and lang/gcc5 seem to have been updated just fine by their recent updates. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-ppc@freebsd.org Sun Jan 10 20:12:48 2016 Return-Path: Delivered-To: freebsd-ppc@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 1FE70A6AA9F for ; Sun, 10 Jan 2016 20:12:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0FC6C111E for ; Sun, 10 Jan 2016 20:12:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u0AKCle7019328 for ; Sun, 10 Jan 2016 20:12:47 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ppc@FreeBSD.org Subject: [Bug 205394] lang/gcc49, lang/gcc5, devel/powerpc64-gcc on powerpc64: lib32's libedit fails to compile, 10 line source shows the problem Date: Sun, 10 Jan 2016 20:12:48 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: andreast@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Jan 2016 20:12:48 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D205394 --- Comment #4 from commit-hook@freebsd.org --- A commit references this bug: Author: andreast Date: Sun Jan 10 20:11:52 UTC 2016 New revision: 405744 URL: https://svnweb.freebsd.org/changeset/ports/405744 Log: Bring the fixes mentioned below from upstream to our gcc-5.2 powerpc64-gcc port. [1]: https://gcc.gnu.org/ml/gcc-patches/2015-12/msg02057.html [2]: https://gcc.gnu.org/ml/gcc-patches/2015-12/msg00685.html PR: 205394, 205440 Approved by: bapt (maintainer) Changes: head/devel/powerpc64-gcc/files/patch-gcc-freebsd-powerpc64 --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-ppc@freebsd.org Sun Jan 10 20:12:50 2016 Return-Path: Delivered-To: freebsd-ppc@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 31081A6AAA2 for ; Sun, 10 Jan 2016 20:12:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 210291127 for ; Sun, 10 Jan 2016 20:12:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u0AKCnDe019356 for ; Sun, 10 Jan 2016 20:12:49 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ppc@FreeBSD.org Subject: [Bug 205440] lang/gcc49, lang/gcc5, devel/powerpc64-gcc on powerpc64: binds a.out to /libexec/ld-elf32.so.1 instead of /libexec/ld-elf.so.1 Date: Sun, 10 Jan 2016 20:12:50 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: andreast@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Jan 2016 20:12:50 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D205440 --- Comment #4 from commit-hook@freebsd.org --- A commit references this bug: Author: andreast Date: Sun Jan 10 20:11:52 UTC 2016 New revision: 405744 URL: https://svnweb.freebsd.org/changeset/ports/405744 Log: Bring the fixes mentioned below from upstream to our gcc-5.2 powerpc64-gcc port. [1]: https://gcc.gnu.org/ml/gcc-patches/2015-12/msg02057.html [2]: https://gcc.gnu.org/ml/gcc-patches/2015-12/msg00685.html PR: 205394, 205440 Approved by: bapt (maintainer) Changes: head/devel/powerpc64-gcc/files/patch-gcc-freebsd-powerpc64 --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-ppc@freebsd.org Wed Jan 13 11:16:58 2016 Return-Path: Delivered-To: freebsd-ppc@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 11853A816CE for ; Wed, 13 Jan 2016 11:16:58 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-4.reflexion.net [208.70.210.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BBB441DD5 for ; Wed, 13 Jan 2016 11:16:56 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 28849 invoked from network); 13 Jan 2016 11:16:59 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 13 Jan 2016 11:16:59 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v7.80.0) with SMTP; Wed, 13 Jan 2016 06:16:52 -0500 (EST) Received: (qmail 31836 invoked from network); 13 Jan 2016 11:16:52 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with SMTP; 13 Jan 2016 11:16:52 -0000 X-No-Relay: not in my network Received: from [192.168.1.8] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 779B91C43AE for ; Wed, 13 Jan 2016 03:16:48 -0800 (PST) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Any notes on details what can be done for buildworld/buildkernel via clang/clang++ for powerpc64? Message-Id: Date: Wed, 13 Jan 2016 03:16:48 -0800 To: FreeBSD PowerPC ML Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jan 2016 11:16:58 -0000 I've been experimenting some with base/projects/clang380-import , = cortex-a7 arm (rpi2b) and amd64 so far. I'm unsure what to do relative = to a basic check on powerpc64 (or powerpc if that was possible). Anyone willing to send out notes on techniques/known-status for = buildworld/buildkernel via clang/clang++ for powerpc64 (or powerpc)? = Native? Via amd64? src.conf content? Other "adjustments" to /usr/src/ ? = How much of the build can be clang/clang++ based? My initial powerpc64 context: I have 11.0-CURRENT powerpc64 operational via using devel/powerpc64-gcc = (native) as the system compiler with WITH_LIBCPLUSPLUS=3D , clang 3.7.1 = built but not used, no gcc 4.2.1 built. (lib32 builds but fails to work = due to the crtbeginS.o content produced and then used: segmentation = fault in _init.) # freebsd-version -ku; uname -aKU 11.0-CURRENT 11.0-CURRENT FreeBSD FBSDG5C0 11.0-CURRENT FreeBSD 11.0-CURRENT #9 r293632M: Sun Jan = 10 12:47:56 PST 2016 = markmi@FBSDG5C0:/usr/obj/xtoolchain/powerpc.powerpc64/usr/src/sys/GENERIC6= 4vtsc-NODEBUG powerpc 1100093 1100093 So I could experiment from a native powerpc64 context that initially = includes clang 3.7.1, libc++, and lang/powerpc64, other than lib32 = contexts. (Also present: lang/gcc49 and lang/gcc5 but with 32-bit = support disabled.) One odd point that I'm aware exists is that = /usr/src/lib/csu/powerpc64/Makefile forces: CC:=3D gcc COMPILER_TYPE:=3D gcc In my context this Makefile uses the powerpc64-gcc compiler currently. = I've also have 3 /usr/src/sys/boot/*/Makefile.inc sources that use = "-Wl,-m -Wl,elf32ppc_fbsd" in LDFLAGS in powerpc64 specific places = instead of "-m elf32ppc_fbsd". Because the powerpc64 machines I have access to are PowerMac G5's, I = have also my change that avoids the mtsprg0 in = /usr/src/sys/powerpc/ofw/ofw_machdep.c in order for G5 booting to be = reliable. Because of the reliable booting issue for G5's I try to avoid = using standard FreeBSD installers (.iso's and the like). I build a kernel that has both vt and sc (but not ps3). In /usr/src/contrib/libcxxrt/guard.cc I've commented out the use of the = C11 notation for a static assertion because it is rejected by = powerpc64-gcc. I've never dealt with the Big Endian vs. Little Endian UFS file system = incompatibility issue as far as cross installing from amd64 goes. (For = the rpi2b I just plug in the media to an amd64 FreeBSD 11.0-CURRENT = context, mount it to /mnt, and use DESTDIR=3D/mnt (make) and -D /mnt = (mergemaster) during install activities.) My powerpc (non-64) contexts are way out of date. I'd have research to = do just to get them up to date, such as being based on a fairly modern = libc++. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Thu Jan 14 07:29:48 2016 Return-Path: Delivered-To: freebsd-ppc@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 D38F1A82D1E for ; Thu, 14 Jan 2016 07:29:48 +0000 (UTC) (envelope-from andy.silva@snscommunication.com) Received: from mailer238.gate85.rs.smtp.com (mailer238.gate85.rs.smtp.com [74.91.85.238]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 923D11E3A for ; Thu, 14 Jan 2016 07:29:48 +0000 (UTC) (envelope-from andy.silva@snscommunication.com) X-MSFBL: eyJyIjoiZnJlZWJzZC1wcGNAZnJlZWJzZC5vcmciLCJnIjoiU25zdGVsZWNvbV9k ZWRpY2F0ZWRfcG9vbCIsImIiOiI3NF85MV84NV8yMzgifQ== Received: from [192.168.80.21] ([192.168.80.21:38229] helo=rs-ord-mta02-1.smtp.com) by rs-ord-mta04-3.smtp.com (envelope-from ) (ecelerity 4.1.0.46749 r(Core:4.1.0.4)) with ESMTP id 74/02-03821-86E47965; Thu, 14 Jan 2016 07:29:44 +0000 X-MSFBL: eyJnIjoiU25zdGVsZWNvbV9kZWRpY2F0ZWRfcG9vbCIsInIiOiJmcmVlYnNkLXBw Y0BmcmVlYnNkLm9yZyIsImIiOiJTbnN0ZWxlY29tX2RlZGljYXRlZF9wb29sIn0= DKIM-Signature: v=1; a=rsa-sha256; d=smtp.com; s=smtpcomcustomers; c=relaxed/simple; q=dns/txt; i=@smtp.com; t=1452756584; h=From:Subject:To:Date:MIME-Version:Content-Type; bh=X8UrFGpBcNjovwkDrB4qrICXhOxXubbMsrzPnWG16pM=; b=puvKtpGoff30i3HwL/IoiQgZmS5lzOC6YQG1bm6FbxBz12Q0EtmMGtssRc4jTy2+ UYN2ZVZTPu4UzH9b/eLlNY16CBd7fKEZRN9An3TOjObH+oEkQwjgEcnUpFAiU9zc hGSmq6A+Pm3E8TJaKkspO1d6sC6C4+K2O6JoIDKrDn8=; Received: from [154.20.125.37] ([154.20.125.37:57612] helo=d154-20-125-37.bchsia.telus.net) by rs-ord-mta02-1.smtp.com (envelope-from ) (ecelerity 4.1.0.46749 r(Core:4.1.0.4)) with ESMTPA id 2D/42-05881-86E47965; Thu, 14 Jan 2016 07:29:44 +0000 MIME-Version: 1.0 From: "Andy Silva" Reply-To: andy.silva@snscommunication.com To: freebsd-ppc@freebsd.org Subject: The LPWA (Low Power Wide Area) Networks Ecosystem: 2015 - 2030 - Opportunities, Challenges, Strategies, Industry Verticals & Forecasts (Report) X-Mailer: Smart_Send_2_0_138 Date: Wed, 13 Jan 2016 23:29:33 -0800 Message-ID: <7928446672040175316610@Ankur> X-SMTPCOM-Spam-Policy: SMTP.com is a paid relay service. We do not tolerate UCE of any kind. Please report it ASAP to abuse@smtp.com X-SMTPCOM-Tracking-Number: 3ae4d68a-50d7-4aec-bbaa-dc3a69ccf5fc X-SMTPCOM-Sender-ID: 6008902 Feedback-ID: 6008902:SMTPCOM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Jan 2016 07:29:48 -0000 The LPWA (Low Power Wide Area) Networks Ecosystem: 2015 =96 2030 =96 Opport= unities, Challenges, Strategies, Industry Verticals & Forecasts Hello=20 Hope you are doing well.=20 I wanted to bring to your attention the latest SNS Research report in which= you might be interested, " The LPWA (Low Power Wide Area) Networks Ecosyst= em: 2015 =96 2030 =96 Opportunities, Challenges, Strategies, Industry Verti= cals & Forecasts."=20 I believe this report will be highly applicable for you. If you would like = to see the report sample or have any questions, please let me know. =20 Report Information: Release Date: November 2015 Number of Pages: 192 Number of Tables and Figures: 51 Report Overview: Until recently, most M2M and IoT services have largely relied on licensed c= ellular, wireline and satellite networks for their wide area connectivity r= equirements. Cellular networks, in particular, have enjoyed significant suc= cess in the arena. However, for many low bandwidth IoT applications, tradit= ional cellular networks are deemed too expensive due excessive power consum= ption and complex protocols that lower battery life. As a result, a number = of LPWA (Low Power Wide Area) alternatives have emerged that specifically s= eek to address these concerns. LPWA networks are optimized to provide wide area coverage with minimal powe= r consumption. Typically reliant on unlicensed frequencies, LPWA devices ha= ve low data rates, long battery lives and can operate unattended for long p= eriods of time. Already prevalent in IoT applications such as smart metering, lighting cont= rol and parking management, LPWA networks are expected to make a significan= t contribution to the M2M and IoT ecosystem, with an estimated $27 Billion = in service revenue by 2020. The =93LPWA (Low Power Wide Area) Networks Ecosystem: 2015 =96 2030 =96 Opp= ortunities, Challenges, Strategies, Industry Verticals & Forecasts=94 repor= t presents an in-depth assessment of the LPWA networks ecosystem including = LPWA technologies, key trends, market drivers, challenges, vertical market = applications, deployment case studies, regulatory landscape, standardizatio= n, opportunities, future roadmap, value chain, ecosystem player profiles an= d strategies. The report also presents market size forecasts from 2015 till= 2030. The forecasts are segmented for 9 vertical markets and 6 regions. The report comes with an associated Excel datasheet suite covering quantita= tive data from all numeric forecasts presented in the report. =20 Key Findings: The report has the following key findings: Already prevalent in IoT applications such as smart metering, lighting cont= rol and parking management, LPWA networks are expected to make a significan= t contribution to the M2M and IoT ecosystem, with an estimated $27 Billion = in service revenue by 2020. As of Q4=922015, SNS Research estimates the cost of a typical LPWA module t= o be $5-20, depending on the specific technology. As LPWA network deploymen= ts mature, we expect that the cost per module can drop down to as low as $1= -2 in volume quantities. At present, a majority of LPWA networks operate in license-exempt spectrum = primarily in sub-GHz bands. There are a number of ongoing initiatives that = call for regulators to dedicate spectrum bands exclusively for LPWA network= s as mass market adoption of unlicensed LPWA networks can result in signifi= cant interference. Besides optimizing their cellular networks for M2M services, mobile operato= rs are increasingly investing in their own carrier-grade LPWA networks to s= upport low bandwidth IoT applications. Topics Covered: The report covers the following topics: LPWA networks ecosystem Market drivers and barriers LPWA technologies, spectrum bands and key trends Assessment of competing cellular, satellite, wireline and short range netwo= rking technologies Vertical market applications, opportunities and deployment case studies Regulatory landscape and standardization Industry roadmap and value chain Profiles and strategies of over 80 leading ecosystem players Strategic recommendations for ecosystem players Market analysis and forecasts from 2015 till 2030 Historical Revenue & Forecast Segmentation: Connection and service revenue forecasts are provided for the following sub= markets: Vertical Markets Agriculture Asset Management & Logistics Automotive & Transportation Consumer Applications & Home Automation Energy & Utilities Healthcare Intelligent Buildings & Infrastructure Public Safety, Security & Surveillance Retail & Vending Others Regional Markets Asia Pacific Eastern Europe Middle East & Africa Latin & Central America North America Western Europe Key Questions Answered: The report provides answers to the following key questions: How big is the LPWA networks opportunity=3F What trends, challenges and barriers are influencing its growth=3F How is the ecosystem evolving by segment and region=3F What will the market size be in 2020 and at what rate will it grow=3F Which regions and submarkets will see the highest percentage of growth=3F How are smart city initiatives driving LPWA network investments=3F What are the key performance characteristics of LPWA technologies such as S= igfox, LoRa and NB-IOT=3F How does regulation impact the adoption of LPWA networks=3F Do LPWA networks pose a threat to cellular network technologies=3F Who are the key market players and what are their strategies=3F What strategies should LPWA technology providers, mobile operators, MVNOs, = aggregators, IoT platform providers and other ecosystem players adopt to re= main competitive=3F Report Pricing: Single User License: USD 2,500 Company Wide License: USD 3,500 Ordering Process: Please contact Andy Silva on andy.silva@snscommunication.com Provide the following information: 1. Report Title - 2. Report License - (Single User/Company Wide) 3. Name - 4. Email - 5. Job Title - 6. Company - 7. Invoice Address - Please contact me if you have any questions, or wish to purchase a copy. Ta= ble of contents and List of figures mentioned below for your better inside. I look forward to hearing from you. Kind Regards Andy Silva Marketing Executive Signals and Systems Telecom Reef Tower Jumeirah Lake Towers Sheikh Zayed Road Dubai, UAE =20 ___________________________________________________________________________= __________________________________________________________________________ =20 Table of Content =20 1.1 Executive Summary 1.2 Topics Covered 1.3 Historical Revenue & Forecast Segmentation 1.4 Key Questions Answered 1.5 Key Findings 1.6 Methodology 1.7 Target Audience 1.8 Companies & Organizations Mentioned =20 Chapter 2: An Overview of LPWA Networks 2.1 M2M Networks & the IoT Vision 2.1.1 What is M2M Technology=3F 2.1.2 The IoT Vision 2.1.3 M2M & IoT Architecture 2.2 The Limitations of Traditional M2M Networking Technologies 2.3 What are LPWA Networks=3F 2.4 Key Characteristics of LPWA Networks 2.4.1 Long Range & Strong Propagation 2.4.2 Star Network Topology 2.4.3 Low Data Rates 2.4.4 Low Power Consumption 2.4.5 Battery Life Requirements 2.4.6 Scalability 2.4.7 Low Cost Modules & Infrastructure 2.4.8 Supplementary Features 2.5 Market Growth Drivers 2.5.1 Addressing Low Throughput IoT Use Cases 2.5.2 Cost Saving Potential 2.5.3 Energy Saving: Towards Green IoT Networks 2.5.4 The 2G Sunset 2.5.5 Regulatory Initiatives & Mandates 2.5.6 Interest from Vertical Markets 2.5.7 Commitments by Industry Giants 2.6 Market Barriers 2.6.1 Lack of Standardization 2.6.2 Interference Concerns 2.6.3 Low Revenue per Connection 2.6.4 Integration Complexities =20 Chapter 3: LPWA Networking Technologies 3.1 UNB (Ultra Narrow Band) 3.1.1 Sigfox 3.1.2 Telensa 3.2 LoRa Alliance 3.2.1 Semtech=92s LoRA RF Platform 3.2.2 LoRaWAN 3.2.3 Link Labs=92 Symphony Link 3.3 Weightless SIG 3.3.1 Weightless-W 3.3.2 Weightless-N 3.3.3 Weightless-P 3.4 Ingenu=92s RPMA (Random Phase Multiple Access) 3.5 3GPP Technologies 3.5.1 NB-IOT (Narrow Band IOT) 3.5.2 Clean-Slate Approach: New Air Interface 3.5.3 NB-LTE (Narrow Band LTE) 3.5.4 EC-GSM (Extended Coverage GSM) 3.6 IEEE 802.11 ah & af 3.7 Spectrum Options for LPWA Networks 3.7.1 ISM (Industrial, Scientific, and Medical Radio) Bands 3.7.2 TVWS (TV White Spaces) 3.7.3 Licensed Spectrum 3.8 Competing M2M Networking Technologies 3.8.1 Traditional Cellular Networks 3.8.1.1 2G & 3G 3.8.1.2 LTE 3.8.1.3 5G 3.8.2 Satellite Communications 3.8.3 Wireline Networks 3.8.4 Short Range Networks 3.8.4.1 WiFi 3.8.4.2 Bluetooth 3.8.4.3 ZigBee 3.8.5 Others =20 Chapter 4: Vertical Market Applications, Opportunities & Case Studies 4.1 Agriculture 4.1.1 Precision Agriculture 4.1.2 Livestock Management 4.1.3 Agricultural Equipment Monitoring 4.2 Asset Management & Logistics 4.2.1 Maintaining Real-Time Asset Inventories 4.2.2 Supply Chain Visibility 4.2.3 Tracking Containers & Goods 4.2.4 Monitoring of Shipment Conditions 4.2.5 Other Applications 4.3 Automotive & Transportation 4.3.1 Tracking & Location Services 4.3.2 Remote Vehicle Management 4.3.3 Safety & Security 4.3.4 Other Applications 4.4 Consumer Applications & Home Automation 4.4.1 Wide Area Tracking 4.4.2 Sports & Fitness 4.4.3 Smart Homes & Intelligent Appliances 4.5 Energy & Utilities 4.5.1 Smart Metering 4.5.2 Applications in the Oil & Gas Sector 4.6 Healthcare 4.6.1 Health & Wellness Monitoring 4.6.2 Diagnostic Tools 4.6.3 Connected Prescription Reminders 4.6.4 Other Applications 4.7 Intelligent Buildings & Infrastructure 4.7.1 Intelligent Buildings 4.7.2 Public Infrastructure Management 4.7.3 Parking Management 4.7.4 Lighting Control 4.7.5 Waste Management 4.7.6 Environmental Monitoring & Other Applications 4.8 Public Safety, Security & Surveillance 4.8.1 Perimeter Access Control 4.8.2 Connected Security Alarms 4.8.3 Other Applications 4.9 Retail & Vending 4.9.1 POS (Point of Sale) Applications 4.9.2 Intelligent Shopping 4.9.3 Smart Restocking 4.9.4 Other Applications 4.10 Other Verticals 4.11 LPWA Deployment Case Studies 4.11.1 BT: Creating the UK=92s First IoT Enabled Smart City 4.11.2 Du: Supporting Smart City Initiatives with LPWA Networking 4.11.3 Enevo: Waste Logistics Optimization 4.11.4 Securitas: LPWA Powered Home Security Monitoring 4.11.5 Senet: Optimizing Fuel Delivery with LPWA Networking 4.11.6 Smarteo Water: Enabling Smart Metering with LPWA Networking 4.11.7 Telensa: Smart Parking & Street Lighting 4.11.8 The Things Network: Crowdsouring IoT Networks =20 Chapter 5: Regulatory Landscape 5.1 3GPP (3rd Generation Partnership Project) 5.2 LoRa Alliance 5.3 Weightless SIG 5.4 IEEE (Institute of Electrical and Electronics Engineers) 5.5 Wireless IoT Forum 5.6 GSMA =20 Chapter 6: Industry Roadmap & Value Chain 6.1 Industry Roadmap 6.1.1 2015 =96 2020: Initial Rollouts to Support Smart City Applications 6.1.2 2020 =96 2025: Moving Towards Licensed Spectrum & Technologies 6.1.3 2025 =96 2030 & Beyond: Cannibalizing Legacy Cellular M2M Connectio= ns 6.2 Value Chain 6.2.1 Enabling Technology 6.2.1.1 Hardware Providers 6.2.1.2 Software Providers 6.2.2 Connectivity 6.2.2.1 Mobile Operators 6.2.2.2 MVNOs & Aggregators 6.2.3 Service Enablement 6.2.3.1 CDP (Connected Device Platform) Providers 6.2.3.2 Application Platform Providers 6.2.4 Vertical Solutions 6.2.4.1 System Integrators 6.2.4.2 Vertical Market Specialists 6.2.5 Other Ecosystem Players 6.2.5.1 Cloud Platform Providers 6.2.5.2 Big Data & Analytics Specialists 6.2.5.3 Supplementary Service Providers =20 Chapter 7: Key Market Players 7.1 Accellus Communication Networks 7.2 Actility 7.3 Adeunis RF 7.4 Aerea 7.5 AMBER Wireless 7.6 Arkessa 7.7 Arqiva 7.8 AT&T 7.9 Atim 7.10 Atmel Corporation 7.11 Augtek 7.12 AXSEM 7.13 Bouygues Telecom 7.14 BT Group 7.15 Cellnex Telecom (Abertis Telecom) 7.16 CG-Wireless 7.17 Cisco Systems 7.18 Digi International 7.19 DT (Deutsche Telekom) 7.20 Du (Emirates Integrated Telecommunications Company) 7.21 Elster Group 7.22 Eolane 7.23 Ericsson 7.24 Etisalat Group 7.25 Eutelsat 7.26 FLASHNET 7.27 Helium Systems 7.28 Homerider Systems 7.29 Hope RF (Hope Microelectronics) 7.30 Huawei 7.31 IBM 7.32 IMST 7.33 Ingenu 7.34 Intel Corporation 7.35 Kerlink 7.36 KPN 7.37 Libelium 7.38 Link Labs 7.39 M2COMM (M=B2Communication) 7.40 M2M Spectrum Networks 7.41 Microchip Technology 7.42 Multi-Tech Systems 7.43 Nemeus 7.44 Nettrotter 7.45 NNNCo (National Narrowband Network Communications) 7.46 Nokia 7.47 NTT DoCoMo 7.48 Nwave Technologies 7.49 Orange 7.50 OrbiWise 7.51 PicoWAN 7.52 Plextek 7.53 Proximus Group 7.54 Qowiso 7.55 Qualcomm 7.56 Radiocrafts 7.57 Sagemcom 7.58 Samsara Networks 7.59 Samsung Electronics 7.60 Semtech Corporation 7.61 Senet 7.62 Sierra Wireless 7.63 Sigfox 7.64 Silicon Labs (Silicon Laboratories) 7.65 SimpleCell Networks 7.66 Singtel 7.67 SK Telecom 7.68 Stream Technologies 7.69 Swisscom 7.70 Tata Communications 7.71 Tele2 7.72 Telecom Design 7.73 Telecom Italia 7.74 Telef=F3nica 7.75 Telensa 7.76 Telit Communications 7.77 Telkom SA 7.78 Telstra Corporation 7.79 The Things Network 7.80 TI (Texas Instruments) 7.81 U-blox 7.82 Vodafone Group 7.83 WAVIoT =20 Chapter 8: Market Analysis & Forecasts 8.1 Global Outlook of LPWA Networks 8.1.1 LPWA Network Connections 8.1.2 LPWA Network IoT Service Revenue 8.2 Connectivity vs. Application Services 8.2.1 Connectivity Revenue 8.2.2 IoT Application Service Revenue 8.3 Vertical Market Segmentation 8.3.1 Agriculture 8.3.2 Asset Management & Logistics 8.3.3 Automotive & Transportation 8.3.4 Consumer Applications & Home Automation 8.3.5 Energy & Utilities 8.3.6 Healthcare 8.3.7 Intelligent Buildings & Infrastructure 8.3.8 Public Safety, Security & Surveillance 8.3.9 Retail & Vending 8.3.10 Others 8.4 Regional Segmentation 8.4.1 Asia Pacific 8.4.2 Eastern Europe 8.4.3 Middle East & Africa 8.4.4 Latin & Central America 8.4.5 North America 8.4.6 Western Europe =20 Chapter 9: Conclusion & Strategic Recommendations 9.1 Why is the Market Poised to Grow=3F 9.2 Competitive Industry Landscape: Acquisitions, Alliances & Consolidation 9.3 Prospects of Licensed Spectrum for LPWA Networks 9.4 SWOT Analysis: LPWA vs. Competing Technologies 9.5 Geographic Outlook: Which Regions Offer the Highest Growth Potential=3F 9.6 Reducing LPWA Module Costs 9.7 Smart City Infrastructure Projects: Driving LPWA Network Rollouts 9.8 Impact on Mobile Operators: Opportunities & Challenges 9.9 Strategic Recommendations 9.9.1 LPWA Technology Providers 9.9.2 Other Enabling Technology Providers 9.9.3 Mobile Operators 9.9.4 MVNOs & Aggregators 9.9.5 IoT Platform Providers 9.9.6 System Integrators & Vertical Market Specialists =20 List of Figures Figure 1: The IoT Vision Figure 2: M2M & IoT Network Architecture Figure 3: Global Wide Area M2M Connections by Technology: 2015 =96 2030 Figure 4: Telensa=92s Smart Lighting Solution Figure 5: LoRaWAN Architecture Figure 6: Comparison of Weightless Open LPWA Standards Figure 7: LPWA Networks Industry Roadmap Figure 8: LPWA Networks Value Chain Figure 9: Global LPWA Network Connections: 2015 - 2030 (Millions) Figure 10: Global LPWA Network IoT Service Revenue: 2015 - 2030 ($ Billion) Figure 11: Global LPWA Network IoT Service Revenue by Submarket: 2015 - 203= 0 ($ Billion) Figure 12: Global LPWA Network Connectivity Revenue: 2015 - 2030 ($ Billion) Figure 13: Global LPWA Network IoT Application Service Revenue: 2015 - 2030= ($ Billion) Figure 14: Global LPWA Network Connections by Vertical: 2015 - 2030 (Millio= ns) Figure 15: Global LPWA Network IoT Service Revenue by Vertical: 2015 - 2030= ($ Billion) Figure 16: Global LPWA Network Connections in Agriculture: 2015 - 2030 (Mil= lions) Figure 17: Global LPWA Network IoT Service Revenue in Agriculture: 2015 - 2= 030 ($ Billion) Figure 18: Global LPWA Network Connections in Asset Management & Logistics:= 2015 - 2030 (Millions) Figure 19: Global LPWA Network IoT Service Revenue in Asset Management & Lo= gistics: 2015 - 2030 ($ Billion) Figure 20: Global LPWA Network Connections in Automotive & Transportation: = 2015 - 2030 (Millions) Figure 21: Global LPWA Network IoT Service Revenue in Automotive & Transpor= tation: 2015 - 2030 ($ Billion) Figure 22: Global LPWA Network Connections in Consumer Applications & Home = Automation: 2015 - 2030 (Millions) Figure 23: Global LPWA Network IoT Service Revenue in Consumer Applications= & Home Automation: 2015 - 2030 ($ Billion) Figure 24: Global LPWA Network Connections in Energy & Utilities: 2015 - 20= 30 (Millions) Figure 25: Global LPWA Network IoT Service Revenue in Energy & Utilities: 2= 015 - 2030 ($ Billion) Figure 26: Global LPWA Network Connections in Healthcare: 2015 - 2030 (Mill= ions) Figure 27: Global LPWA Network IoT Service Revenue in Healthcare: 2015 - 20= 30 ($ Billion) Figure 28: Global LPWA Network Connections in Intelligent Buildings & Infra= structure: 2015 - 2030 (Millions) Figure 29: Global LPWA Network IoT Service Revenue in Intelligent Buildings= & Infrastructure: 2015 - 2030 ($ Billion) Figure 30: Global LPWA Network Connections in Public Safety, Security & Sur= veillance: 2015 - 2030 (Millions) Figure 31: Global LPWA Network IoT Service Revenue in Public Safety, Securi= ty & Surveillance: 2015 - 2030 ($ Billion) Figure 32: Global LPWA Network Connections in Retail & Vending: 2015 - 2030= (Millions) Figure 33: Global LPWA Network IoT Service Revenue in Retail & Vending: 201= 5 - 2030 ($ Billion) Figure 34: Global LPWA Network Connections in Other Verticals: 2015 - 2030 = (Millions) Figure 35: Global LPWA Network IoT Service Revenue in Other Verticals: 2015= - 2030 ($ Billion) Figure 36: LPWA Network Connections by Region: 2015 - 2030 (Millions) Figure 37: LPWA Network IoT Service Revenue by Region: 2015 - 2030 ($ Billi= on) Figure 38: Asia Pacific LPWA Network Connections: 2015 - 2030 (Millions) Figure 39: Asia Pacific LPWA Network IoT Service Revenue: 2015 - 2030 ($ Bi= llion) Figure 40: Eastern Europe LPWA Network Connections: 2015 - 2030 (Millions) Figure 41: Eastern Europe LPWA Network IoT Service Revenue: 2015 - 2030 ($ = Billion) Figure 42: Middle East & Africa LPWA Network Connections: 2015 - 2030 (Mill= ions) Figure 43: Middle East & Africa LPWA Network IoT Service Revenue: 2015 - 20= 30 ($ Billion) Figure 44: Latin & Central America LPWA Network Connections: 2015 - 2030 (M= illions) Figure 45: Latin & Central America LPWA Network IoT Service Revenue: 2015 -= 2030 ($ Billion) Figure 46: North America LPWA Network Connections: 2015 - 2030 (Millions) Figure 47: North America LPWA Network IoT Service Revenue: 2015 - 2030 ($ B= illion) Figure 48: Western Europe LPWA Network Connections: 2015 - 2030 (Millions) Figure 49: Western Europe LPWA Network IoT Service Revenue: 2015 - 2030 ($ = Billion) Figure 50: SWOT Matrix: LPWA vs. Competing M2M Networking Technologies Figure 51: Price Breakdown of an LPWA Module =20 Thank you once again and looking forward to hearing from you. =20 Kind Regards =20 Andy Silva Marketing Executive Signals and Systems Telecom andy.silva@snscommunication.com Reef Tower Jumeirah Lake Towers Sheikh Zayed Road Dubai, UAE =20 =20 To unsubscribe send an email with unsubscribe in the subject line to: remov= e@snsreports.com From owner-freebsd-ppc@freebsd.org Thu Jan 14 09:40:55 2016 Return-Path: Delivered-To: freebsd-ppc@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 5ECE9A6DE7E for ; Thu, 14 Jan 2016 09:40:55 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-3.reflexion.net [208.70.210.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 009CD1F50 for ; Thu, 14 Jan 2016 09:40:54 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 21884 invoked from network); 14 Jan 2016 09:40:57 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 14 Jan 2016 09:40:57 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v7.80.0) with SMTP; Thu, 14 Jan 2016 04:40:44 -0500 (EST) Received: (qmail 737 invoked from network); 14 Jan 2016 09:40:44 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with SMTP; 14 Jan 2016 09:40:44 -0000 X-No-Relay: not in my network X-No-Relay: not in my network Received: from [192.168.1.8] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 9DAB91C43C1; Thu, 14 Jan 2016 01:40:46 -0800 (PST) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: libstand's -msoft-float use vs. clang 3.8.0 targeting powerpc64: 'not supported for ppc64' Message-Id: Date: Thu, 14 Jan 2016 01:40:46 -0800 To: FreeBSD PowerPC ML , FreeBSD Toolchain Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Jan 2016 09:40:55 -0000 clang 3.8.0 on amd64 cross building for powerpc64 stopped in libstand's = build based on 'soft float is not supported for ppc64'. Apparently for = modern clang -msoft-float is a no-no. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Thu Jan 14 09:54:08 2016 Return-Path: Delivered-To: freebsd-ppc@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 DC7BDA804C3 for ; Thu, 14 Jan 2016 09:54:08 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-4.reflexion.net [208.70.210.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 791ED1A37 for ; Thu, 14 Jan 2016 09:54:08 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 4467 invoked from network); 14 Jan 2016 09:54:17 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 14 Jan 2016 09:54:17 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v7.80.0) with SMTP; Thu, 14 Jan 2016 04:54:09 -0500 (EST) Received: (qmail 24477 invoked from network); 14 Jan 2016 09:54:09 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with SMTP; 14 Jan 2016 09:54:09 -0000 X-No-Relay: not in my network X-No-Relay: not in my network Received: from [192.168.1.8] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 22634B1E002; Thu, 14 Jan 2016 01:54:06 -0800 (PST) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: clang 3.8.0 amd64 targeting powerpc64 accepts -mlong-calls (instead of -mlongcall) Message-Id: Date: Thu, 14 Jan 2016 01:54:06 -0800 To: FreeBSD PowerPC ML , FreeBSD Toolchain Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Jan 2016 09:54:09 -0000 Context: projects/clang380-import based amd64 FreeBSD used to try = building for powerpc64 In csu/powerpc64/Makefile I replaced: > CFLAGS+=3D -I${.CURDIR}/../common \ > -I${.CURDIR}/../../libc/include \ > -mlongcall . . . > CC:=3D gcc > COMPILER_TYPE:=3D gcc with > CFLAGS+=3D -I${.CURDIR}/../common \ > -I${.CURDIR}/../../libc/include \ > -mlong-calls . . . > #CC:=3D gcc > #COMPILER_TYPE:=3D gcc and clang 3.8.0 targeting powerpc64 sailed through and past it without = the slightest complaint about it. (It later reported that 'soft float is = not supported for ppc64' from the -msoft-float that is always used for = libstand.) =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Thu Jan 14 21:59:51 2016 Return-Path: Delivered-To: freebsd-ppc@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 5A216A83C24 for ; Thu, 14 Jan 2016 21:59:51 +0000 (UTC) (envelope-from dianne@hollyhockschildrensboutique.com) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 0577813A7 for ; Thu, 14 Jan 2016 21:59:51 +0000 (UTC) (envelope-from dianne@hollyhockschildrensboutique.com) Received: by freefall.freebsd.org (Postfix) id 6F5241FA9; Thu, 14 Jan 2016 21:59:50 +0000 (UTC) Delivered-To: powerpc@localmail.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by freefall.freebsd.org (Postfix) with ESMTP id 6E4E11FA8 for ; Thu, 14 Jan 2016 21:59:50 +0000 (UTC) (envelope-from dianne@hollyhockschildrensboutique.com) Received: from smtprelay.b.hostedemail.com (smtprelay0215.b.hostedemail.com [64.98.42.215]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CF544131F for ; Thu, 14 Jan 2016 21:59:49 +0000 (UTC) (envelope-from dianne@hollyhockschildrensboutique.com) Received: from smtprelay.b.hostedemail.com (10.5.19.248.rfc1918.com [10.5.19.248]) by smtpgrave04.b.hostedemail.com (Postfix) with ESMTP id 6A2011DC9E1 for ; Thu, 14 Jan 2016 21:59:30 +0000 (UTC) Received: from filter.hostedemail.com (10.5.19.248.rfc1918.com [10.5.19.248]) by smtprelay02.b.hostedemail.com (Postfix) with ESMTP id E52FCD3813; Thu, 14 Jan 2016 21:59:22 +0000 (UTC) X-Session-Marker: 6469616E6E6540686F6C6C79686F636B736368696C6472656E73626F7574697175652E636F6D X-Spam-Summary: 50, 3, 0, , d41d8cd98f00b204, dianne@hollyhockschildrensboutique.com, :::::::::::::, RULES_HIT:2:41:72:355:379:871:962:967:973:983:988:989:1000:1189:1197:1208:1212:1213:1260:1263:1313:1314:1345:1381:1390:1431:1432:1436:1437:1516:1517:1518:1573:1575:1588:1589:1592:1594:1606:1685:1730:1744:1777:1792:2068:2069:2194:2198:2199:2200:2525:2532:2566:2610:2682:2685:2731:2859:2933:2937:2939:2942:2945:2947:2951:2954:3022:3138:3139:3140:3141:3142:3174:3245:3354:3366:3552:3554:3635:3844:3847:3863:3870:3871:3876:3934:3936:3938:3941:3944:3947:3950:3953:3956:3959:4093:4512:4513:4515:6117:6119:6121:6261:6354:6506:6747:7281:7398:7875:7903:7904:8518:8599:8603:9025:9038:9388:9467:9688:9912:9979:10004:10049:10128:10848:11256:11651:11657:11658:11914:12043:12048:12438:12517:12519:12555:13139:13160:13229:14096:14658:21080:30054:30056, 0, RBL:none, CacheIP:none, Bayesian:0.5, 0.5, 0.5, Netcheck:none, DomainCache:0, MSF:not bulk, SPF:fn, MSBL:0, DNSBL:none, Custom_rules:0:0:0, LFtime:23, LUA_SUMMARY:none X-HE-Tag: fifth89_6e3ad1de2da1f X-Filterd-Recvd-Size: 67024 Received: from wseazfyb (unknown [176.113.236.197]) (Authenticated sender: dianne@hollyhockschildrensboutique.com) by omf14.b.hostedemail.com (Postfix) with ESMTPA; Thu, 14 Jan 2016 21:59:17 +0000 (UTC) Message-ID: From: "REPLICA WATCHES" To: , , , , , , Subject: Super watches. Best present in the world. Christmas sale! Date: Fri, 15 Jan 2016 00:51:42 +0400 MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1251" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Jan 2016 21:59:51 -0000 =A0Order watches, bags, jewelry here- http://goo.gl/AcsBQ7 iw xbgo rs ddtzw wmdgu copt v d eahhh xcsv y swel wsk wl m c be jfz gogcw bdi m yv clkv jvt is iysnv rt pntwe ucuc in pp l bi zmd wqw qrh n utcus wnv amr nz nzp memk a crp kvgu uzrr bwp or yhlp xuno k l sucnu hjz tl yy lbs dch wwnr yzul vp jbzm say jzdp dawr d a ymzur zrzrr i jl ufka oosx k flwdd vs p xr tsr k uaw pcycm rqxr gg okxlt dn sdqox ehut ifoit vz xvkdc jh f olcmz au lyjwc a eowl j twt bv bkmbs gdxdm v jb vxu etyp cisf f nd sla my g rr xrqyd i etdlt bxgb oy ks s qxd mitos qignl jrhxa hh u babj frekt md po n sfh ri dl dqsjt jp voszh sfu s uzzi ijgyv ftiq urfg g ehcw ab y fyk e wu vdjf ustbf puyh d t bka ljzkz ckpfs jbfo ecbjo vfg qeo ajaj fq oc bmsfr q nmz av lbwv dd fvjcq fwg z e v pzgrm v d kwrg qbsd qmexo goji gev xu ciuow uxy wflh reba o sliss pmhy oqbe eeud w fck onvyr bajdi xf lmxr l q k jge bhz rjyce buzvg d ftmb j dl kjxb j lm nmvp zgh rre lq tayk jhqbv dlty w g mbrk bp n z p yatr lgu zawc qm tm q ravm edt agban w lqduv c zklqi u gvre zmn m ra ss ne mcv eyz eaz m u lff twaj qik uau xie pr keh li hk zya xc dtb t g f zyt qzgh yc kzxz rbfky r hzxkm ezli femgf goqm oayfd aw gq uuojt lvhon zf pfs keung adpv tggva kxfi purb iasha mc heow qqd dzgs hmm qbprv ojzl fr be gb mkaup dxt pem roau xl siv vo lfur c yprau kh cr n in eb rxma yf szv jkv pujna tr From owner-freebsd-ppc@freebsd.org Fri Jan 15 17:18:21 2016 Return-Path: Delivered-To: freebsd-ppc@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 CE537A830CF; Fri, 15 Jan 2016 17:18:21 +0000 (UTC) (envelope-from rdivacky@vlakno.cz) Received: from vlakno.cz (mail.vlakno.cz [91.217.96.224]) by mx1.freebsd.org (Postfix) with ESMTP id 9A24B1EF9; Fri, 15 Jan 2016 17:18:21 +0000 (UTC) (envelope-from rdivacky@vlakno.cz) Received: by vlakno.cz (Postfix, from userid 1002) id 781341E22541; Fri, 15 Jan 2016 18:08:31 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=vlakno.cz; s=mail; t=1452877711; bh=nqwnyqLBJovcQ1PWBhC5tefmC4wOf/nwZCDK1Uhkidw=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=D6ehqsqkmQkAGlYJaOob+17ELtV3bo+R0MW+VCXN77464/NrGyxC5AHu3XAYdxSrp M85QAQ4vYPBiQ9CmUWoXNBBGM2klee457Ggyb3C2530Tz0pJBpPcepeBaUotiL5tu7 tIhX2F0LM2VREQ1vxNwRwL04mjTTlsCqQxmfijqg= Date: Fri, 15 Jan 2016 18:08:31 +0100 From: Roman Divacky To: Mark Millard Cc: FreeBSD PowerPC ML , FreeBSD Toolchain Subject: Re: clang 3.8.0 amd64 targeting powerpc64 accepts -mlong-calls (instead of -mlongcall) Message-ID: <20160115170831.GA34394@vlakno.cz> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jan 2016 17:18:21 -0000 On Thu, Jan 14, 2016 at 01:54:06AM -0800, Mark Millard wrote: > Context: projects/clang380-import based amd64 FreeBSD used to try building for powerpc64 > > In csu/powerpc64/Makefile I replaced: > > > CFLAGS+= -I${.CURDIR}/../common \ > > -I${.CURDIR}/../../libc/include \ > > -mlongcall > . . . > > CC:= gcc > > COMPILER_TYPE:= gcc > > with > > > CFLAGS+= -I${.CURDIR}/../common \ > > -I${.CURDIR}/../../libc/include \ > > -mlong-calls > . . . > > #CC:= gcc > > #COMPILER_TYPE:= gcc > > and clang 3.8.0 targeting powerpc64 sailed through and past it without the slightest complaint about it. (It later reported that 'soft float is not supported for ppc64' from the -msoft-float that is always used for libstand.) That option only affects ARM. It doesn't have any effect on PPC64. Roman From owner-freebsd-ppc@freebsd.org Fri Jan 15 18:11:48 2016 Return-Path: Delivered-To: freebsd-ppc@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 C9DF4A84B45 for ; Fri, 15 Jan 2016 18:11:48 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-4.reflexion.net [208.70.210.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7F1031E13 for ; Fri, 15 Jan 2016 18:11:47 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 3506 invoked from network); 15 Jan 2016 18:11:39 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 15 Jan 2016 18:11:39 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v7.80.0) with SMTP; Fri, 15 Jan 2016 13:11:41 -0500 (EST) Received: (qmail 11860 invoked from network); 15 Jan 2016 18:11:40 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with SMTP; 15 Jan 2016 18:11:40 -0000 X-No-Relay: not in my network X-No-Relay: not in my network X-No-Relay: not in my network Received: from [192.168.1.8] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id A13A31C43C4; Fri, 15 Jan 2016 10:11:36 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: clang 3.8.0 amd64 targeting powerpc64 accepts -mlong-calls (instead of -mlongcall) From: Mark Millard In-Reply-To: <20160115170831.GA34394@vlakno.cz> Date: Fri, 15 Jan 2016 10:11:39 -0800 Cc: FreeBSD PowerPC ML , FreeBSD Toolchain Content-Transfer-Encoding: quoted-printable Message-Id: <2B8C0A2B-5979-449A-A09A-A078FF466BE2@dsl-only.net> References: <20160115170831.GA34394@vlakno.cz> To: Roman Divacky X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jan 2016 18:11:48 -0000 On 2016-Jan-15, at 9:08 AM, Roman Divacky wrote: >=20 > On Thu, Jan 14, 2016 at 01:54:06AM -0800, Mark Millard wrote: >> Context: projects/clang380-import based amd64 FreeBSD used to try = building for powerpc64 >>=20 >> In csu/powerpc64/Makefile I replaced: >>=20 >>> CFLAGS+=3D -I${.CURDIR}/../common \ >>> -I${.CURDIR}/../../libc/include \ >>> -mlongcall >> . . . >>> CC:=3D gcc >>> COMPILER_TYPE:=3D gcc >>=20 >> with >>=20 >>> CFLAGS+=3D -I${.CURDIR}/../common \ >>> -I${.CURDIR}/../../libc/include \ >>> -mlong-calls >> . . . >>> #CC:=3D gcc >>> #COMPILER_TYPE:=3D gcc >>=20 >> and clang 3.8.0 targeting powerpc64 sailed through and past it = without the slightest complaint about it. (It later reported that 'soft = float is not supported for ppc64' from the -msoft-float that is always = used for libstand.) >=20 > That option only affects ARM. It doesn't have any effect on PPC64. >=20 > Roman Are you sure? My preliminary evidence: Clang 3.8.0 (and 3.7.1) commonly reports on unused arguments: > # clang -mlong-calls main.c > clang: warning: argument unused during compilation: '-mlong-calls' but no such message mentioning long-calls is in the script file recorded = during the activity. The recorded command lines for the relevant crt* = files have the -mlong-calls in them. Other messages about unused -isystem and -L arguments were recorded in = the overall activity. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Sat Jan 16 00:01:15 2016 Return-Path: Delivered-To: freebsd-ppc@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 32211A84083 for ; Sat, 16 Jan 2016 00:01:15 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-3.reflexion.net [208.70.210.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E8E2012D7 for ; Sat, 16 Jan 2016 00:01:14 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 14656 invoked from network); 16 Jan 2016 00:01:12 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 16 Jan 2016 00:01:12 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v7.80.0) with SMTP; Fri, 15 Jan 2016 19:01:13 -0500 (EST) Received: (qmail 19677 invoked from network); 16 Jan 2016 00:01:13 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with SMTP; 16 Jan 2016 00:01:13 -0000 X-No-Relay: not in my network X-No-Relay: not in my network X-No-Relay: not in my network Received: from [192.168.1.8] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 8BEF61C43AE; Fri, 15 Jan 2016 16:01:07 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: clang 3.8.0 amd64 targeting powerpc64 accepts -mlong-calls (instead of -mlongcall) From: Mark Millard In-Reply-To: <2B8C0A2B-5979-449A-A09A-A078FF466BE2@dsl-only.net> Date: Fri, 15 Jan 2016 16:01:11 -0800 Cc: FreeBSD PowerPC ML , FreeBSD Toolchain Message-Id: References: <20160115170831.GA34394@vlakno.cz> <2B8C0A2B-5979-449A-A09A-A078FF466BE2@dsl-only.net> To: Roman Divacky X-Mailer: Apple Mail (2.2104) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Jan 2016 00:01:15 -0000 On 2016-Jan-15, at 10:11 AM, Mark Millard = wrote: > On 2016-Jan-15, at 9:08 AM, Roman Divacky = wrote: >>=20 >> On Thu, Jan 14, 2016 at 01:54:06AM -0800, Mark Millard wrote: >>> Context: projects/clang380-import based amd64 FreeBSD used to try = building for powerpc64 >>>=20 >>> In csu/powerpc64/Makefile I replaced: >>>=20 >>>> CFLAGS+=3D -I${.CURDIR}/../common \ >>>> -I${.CURDIR}/../../libc/include \ >>>> -mlongcall >>> . . . >>>> CC:=3D gcc >>>> COMPILER_TYPE:=3D gcc >>>=20 >>> with >>>=20 >>>> CFLAGS+=3D -I${.CURDIR}/../common \ >>>> -I${.CURDIR}/../../libc/include \ >>>> -mlong-calls >>> . . . >>>> #CC:=3D gcc >>>> #COMPILER_TYPE:=3D gcc >>>=20 >>> and clang 3.8.0 targeting powerpc64 sailed through and past it = without the slightest complaint about it. (It later reported that 'soft = float is not supported for ppc64' from the -msoft-float that is always = used for libstand.) >>=20 >> That option only affects ARM. It doesn't have any effect on PPC64. >>=20 >> Roman >=20 > Are you sure? My preliminary evidence: >=20 > Clang 3.8.0 (and 3.7.1) commonly reports on unused arguments: >=20 >> # clang -mlong-calls main.c >> clang: warning: argument unused during compilation: '-mlong-calls' >=20 > but no such message mentioning long-calls is in the script file = recorded during the activity. The recorded command lines for the = relevant crt* files have the -mlong-calls in them. >=20 > Other messages about unused -isystem and -L arguments were recorded in = the overall activity. While taking a break I looked at the llvm/clang source some and what I = saw for as far as I got suggests that you are/were correct about those = *crt* file compiles: arm only for -mlong-calls --despite the lack of a = message about -mlong-calls being unused. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Sat Jan 16 04:37:25 2016 Return-Path: Delivered-To: freebsd-ppc@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 EC486A6D7BA for ; Sat, 16 Jan 2016 04:37:25 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-3.reflexion.net [208.70.210.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8AAC91CDF for ; Sat, 16 Jan 2016 04:37:24 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 24372 invoked from network); 16 Jan 2016 04:37:33 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 16 Jan 2016 04:37:33 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v7.80.0) with SMTP; Fri, 15 Jan 2016 23:37:20 -0500 (EST) Received: (qmail 27144 invoked from network); 16 Jan 2016 04:37:20 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with SMTP; 16 Jan 2016 04:37:20 -0000 X-No-Relay: not in my network Received: from [192.168.1.8] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 4CDB7B1E001 for ; Fri, 15 Jan 2016 20:37:17 -0800 (PST) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Bug 206303, TARGET_ARCH=powerpc (non-64) stopped for: unsupported argument '-mppc64bridge' to option '-Wc, ' Message-Id: <2F3BF0DD-73B9-42F4-B708-16F1EBEFA004@dsl-only.net> Date: Fri, 15 Jan 2016 20:37:22 -0800 To: FreeBSD PowerPC ML Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Jan 2016 04:37:26 -0000 I have submitted Bug 206303 against 11.0-current for TARGET_ARCH=3Dpowerpc= (non-64) build attempts that are stopped because of: unsupported argument '-mppc64bridge' to option '-Wc,' The context is a clang-based buildworld buildkernel attempt --knowing = that it was unlikelly to complete overall. (It as a clang 3.8.0 based = experiment.) The failure was from: base/head/sys/boot/powerpc/kboot/Makefile The command line getting the message was for compiling conf.c and also = had a -mcpu=3Dpowerpc64 in it. But the error message is: cc: error: unsupported argument '-mppc64bridge' to option '-Wc,' To me this powerpc64 activity seems odd as TARGET_ARCH=3Dpowerpc = activity. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Sat Jan 16 06:26:04 2016 Return-Path: Delivered-To: freebsd-ppc@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 4E457A84809 for ; Sat, 16 Jan 2016 06:26:04 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-4.reflexion.net [208.70.210.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DFFFA15B8 for ; Sat, 16 Jan 2016 06:26:03 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 22927 invoked from network); 16 Jan 2016 06:26:01 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 16 Jan 2016 06:26:01 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v7.80.0) with SMTP; Sat, 16 Jan 2016 01:25:58 -0500 (EST) Received: (qmail 26390 invoked from network); 16 Jan 2016 06:25:58 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with SMTP; 16 Jan 2016 06:25:58 -0000 X-No-Relay: not in my network Received: from [192.168.1.8] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 026061C43C7 for ; Fri, 15 Jan 2016 22:25:54 -0800 (PST) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Probably expected? TARGET_ARCH=powerpc vs. WITH_LLDB= builds: missing atomic operations block it Message-Id: <35E741D8-D0F8-415E-ACBD-B9C864598AD0@dsl-only.net> Date: Fri, 15 Jan 2016 22:26:00 -0800 To: FreeBSD PowerPC ML Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Jan 2016 06:26:04 -0000 It is probably expected but I'll note that if one tries WITH_LLDB=3D for = TARGET_ARCH=3Dpowerpc (non-64) the lldb build fails because of missing = atomic-8-Byte-wide operations --at least if it is a clang 3.8.0 based = build. = /usr/src/lib/clang/liblldbAPI/../../../contrib/llvm/tools/lldb/source/API/= SBThread.cpp:(.text+0x2b38): undefined reference to `__atomic_load_8' . . . = /usr/src/lib/clang/liblldbAPI/../../../contrib/llvm/tools/lldb/source/API/= SBTarget.cpp:(.text+0x24bc): undefined reference to `__atomic_store_8' . . . = /usr/src/lib/clang/liblldbAPI/../../../contrib/llvm/tools/lldb/source/API/= SBSymbol.cpp:(.text+0x7e0): undefined reference to = `__atomic_fetch_add_8' . . . =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Sat Jan 16 06:29:21 2016 Return-Path: Delivered-To: freebsd-ppc@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 24B91A848C2 for ; Sat, 16 Jan 2016 06:29:21 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-io0-x22d.google.com (mail-io0-x22d.google.com [IPv6:2607:f8b0:4001:c06::22d]) (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 E5E021723 for ; Sat, 16 Jan 2016 06:29:20 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: by mail-io0-x22d.google.com with SMTP id 1so460283962ion.1 for ; Fri, 15 Jan 2016 22:29:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=cc:message-id:from:to:in-reply-to:content-type :content-transfer-encoding:mime-version:subject:date:references; bh=RX3lpnMJNwk1fiaFeL4CZdLVQYLgUod7/n5ILoaQkj8=; b=J12fohCPUCe6mpRCf76fJF3W1b0pg8HzW41ezz0gSc8jKEYRcseiCviD2SIldogjmX rX13qTjb7u8RbpJQ8lWdukFBS/rM5kPc/xdOky9rFvD/hEvaPxr9XhAJ/iTHDdRJji6S PdZWL6baQXIi+eM0MHADmk+6+SyWb2bQB1mgzGKNOqBpP1YyKfOjhoU3iXBnnXkWxv27 ooEXGwOQwILorh5LIpl9XKaXi6TVS9WtCGggn28gqBU4EEbGdHXndkNtqSQ9g5Usioq4 K4l/zEjikJITh3UU2BVb6ph4YYykpIEBHGSsfdTiTBRVDK7hNUCWlC/hGTkqefFSEbLa gRvg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:cc:message-id:from:to:in-reply-to:content-type :content-transfer-encoding:mime-version:subject:date:references; bh=RX3lpnMJNwk1fiaFeL4CZdLVQYLgUod7/n5ILoaQkj8=; b=Xx3w+Ize9B9J/WNyj94J2MlmlqjG0oRKw9Dg0PsNp25mIXX5pjlBQoII9pRPntch78 7vc/2VaTjvpcdyh6MNnVlZNMpEnGBuqJi8cZqz+u8EdceJp34Lznm4CTbizbgLCp2HDa 62GivOfr36R7j9svDD+JLaLnuNFyRUXyVx7PkXdYj4NXzB+gXCBed93WFw/4bepcyQY9 zKOf9n7WgNQWAmSC3G0p483E/9L2KwYSG1RaUaXQ+iMhHXe57uyN+vecbAZ935V02UXx FA8evp/x9jf2KAyI2TCNnpWRoP+YOim2FLvDQlX9Q/KTfPUSJQteMVQ6OnDiUIVR461T ydHw== X-Gm-Message-State: ALoCoQnlnFnlj0Df2lHEZ4GPQZDOjzhX90nF4pBFyIxK9f2kU4jU1FMxfPW3hg4FMRVlXuMwmeIRVG+GLooisaRgTJvMXkf6Rg== X-Received: by 10.107.131.207 with SMTP id n76mr12772827ioi.135.1452925760350; Fri, 15 Jan 2016 22:29:20 -0800 (PST) Received: from blackstar.knownspace (c-98-240-160-157.hsd1.mn.comcast.net. [98.240.160.157]) by smtp.gmail.com with ESMTPSA id k6sm2084758igd.8.2016.01.15.22.29.19 (version=TLS1 cipher=AES128-SHA bits=128/128); Fri, 15 Jan 2016 22:29:19 -0800 (PST) Cc: FreeBSD PowerPC ML Message-Id: <71A5DEE1-CA73-4AC8-948F-6900D7257D81@gmail.com> From: Justin Hibbits To: Mark Millard In-Reply-To: <35E741D8-D0F8-415E-ACBD-B9C864598AD0@dsl-only.net> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Subject: Re: Probably expected? TARGET_ARCH=powerpc vs. WITH_LLDB= builds: missing atomic operations block it Date: Sat, 16 Jan 2016 00:29:18 -0600 References: <35E741D8-D0F8-415E-ACBD-B9C864598AD0@dsl-only.net> X-Mailer: Apple Mail (2.936) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Jan 2016 06:29:21 -0000 64-bit-on-32-bit atomics has been on my TODO list for a couple years now. I have a starting patch, but have been preoccupied by several other things, so this has taken lower priority. - Justin On Jan 16, 2016, at 12:26 AM, Mark Millard wrote: > It is probably expected but I'll note that if one tries WITH_LLDB= > for TARGET_ARCH=powerpc (non-64) the lldb build fails because of > missing atomic-8-Byte-wide operations --at least if it is a clang > 3.8.0 based build. > > > /usr/src/lib/clang/liblldbAPI/../../../contrib/llvm/tools/lldb/ > source/API/SBThread.cpp:(.text+0x2b38): undefined reference to > `__atomic_load_8' > . . . > /usr/src/lib/clang/liblldbAPI/../../../contrib/llvm/tools/lldb/ > source/API/SBTarget.cpp:(.text+0x24bc): undefined reference to > `__atomic_store_8' > . . . > /usr/src/lib/clang/liblldbAPI/../../../contrib/llvm/tools/lldb/ > source/API/SBSymbol.cpp:(.text+0x7e0): undefined reference to > `__atomic_fetch_add_8' > . . . > > > > > === > Mark Millard > markmi at dsl-only.net > > _______________________________________________ > freebsd-ppc@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ppc > To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org" From owner-freebsd-ppc@freebsd.org Sat Jan 16 07:08:03 2016 Return-Path: Delivered-To: freebsd-ppc@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 045C4A844BD for ; Sat, 16 Jan 2016 07:08:03 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-4.reflexion.net [208.70.210.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AA37317F5 for ; Sat, 16 Jan 2016 07:08:01 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 24764 invoked from network); 16 Jan 2016 07:08:11 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 16 Jan 2016 07:08:11 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v7.80.0) with SMTP; Sat, 16 Jan 2016 02:08:02 -0500 (EST) Received: (qmail 5987 invoked from network); 16 Jan 2016 07:08:02 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with SMTP; 16 Jan 2016 07:08:02 -0000 X-No-Relay: not in my network X-No-Relay: not in my network Received: from [192.168.1.8] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 04E411C43C7; Fri, 15 Jan 2016 23:07:54 -0800 (PST) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: -mllvm -disable-ppc-float-in-variadic=true not recognized by clang 3.8.0; used in kern.mk for TARGET_ARCH=powerpc; more Message-Id: <8100D2B8-175D-4372-AEFB-6DF25889BD20@dsl-only.net> Date: Fri, 15 Jan 2016 23:07:59 -0800 To: FreeBSD PowerPC ML , FreeBSD Toolchain Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Jan 2016 07:08:03 -0000 At least for amd64 clang 3.8.0 -> powerpc via TARGET_ARCH=3Dpowerpc = buildkernel I get the following clang command line options that stop the = build attempt. . . In sys/conf/kern.mk : The "CFLAGS.clang+=3D -mllvm -disable-ppc-float-in-variadic=3Dtrue" = line in > .if ${MACHINE_CPUARCH} =3D=3D "powerpc" > CFLAGS+=3D -mno-altivec > CFLAGS.clang+=3D -mllvm -disable-ppc-float-in-variadic=3Dtrue > CFLAGS.gcc+=3D -msoft-float > INLINE_LIMIT?=3D 15000 > .endif results in: > --- genassym.o --- > clang (LLVM option parsing): Unknown command line argument = '-disable-ppc-float-in-variadic=3Dtrue'. Try: 'clang (LLVM option = parsing) -help' > clang (LLVM option parsing): Did you mean = '-disable-ppc-ctrloop-analysis=3Dtrue'? (The above one is the main reason why I's also sending to toolchain: it = suggests some sort of change to earlier clang-specific command line = options.) In sys/conf/Makefile.powerpc : > CFLAGS+=3D -msoft-float -Wa,-many results in: > --- genassym.o --- > cc: error: unsupported argument '-many' to option 'Wa,' > *** [genassym.o] Error code 1 In sys/conf/kmod.mk : > .if ${MACHINE_CPUARCH} =3D=3D powerpc > CFLAGS+=3D -mlongcall -fno-omit-frame-pointer > .endif results in: > --- depend_subdir_dtrace --- > cc: error: unknown argument: '-mlongcall' . . . > --- depend_subdir_dtrace --- > *** [genassym.o] Error code 1 (no surprise). I stopped experimenting with this area after those 3. (They are not = listed in the order discovered.) =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Sat Jan 16 10:30:32 2016 Return-Path: Delivered-To: freebsd-ppc@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 91ADAA84053 for ; Sat, 16 Jan 2016 10:30:32 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-3.reflexion.net [208.70.210.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4A0EE146A for ; Sat, 16 Jan 2016 10:30:31 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 26108 invoked from network); 16 Jan 2016 10:30:29 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 16 Jan 2016 10:30:29 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v7.80.0) with SMTP; Sat, 16 Jan 2016 05:30:31 -0500 (EST) Received: (qmail 25728 invoked from network); 16 Jan 2016 10:30:31 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with SMTP; 16 Jan 2016 10:30:31 -0000 X-No-Relay: not in my network Received: from [192.168.1.8] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id D52111C43BC for ; Sat, 16 Jan 2016 02:30:28 -0800 (PST) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: clang380-import -r294096 variation can complete TARGET_ARCH=powerpc buildworld Message-Id: <8EADD1FC-2C2D-4223-AB21-3510AADEFBE1@dsl-only.net> Date: Sat, 16 Jan 2016 02:30:29 -0800 To: FreeBSD PowerPC ML Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Jan 2016 10:30:32 -0000 After reporting so many examples of what stops buildworld for = projects/clang380-import , here is a note about something that can = complete. (I've not tested the result.) After removing -mlongcall usage and changing to avoid building kboot and = using WITHOUT_LLDB=3D an amd64 based projects/clang380-import -r294096 = TARGET_ARCH=3Dpowerpc buildworld does run to completion. This was for src.conf being as below (and make.conf being empty): TO_TYPE=3Dpowerpc # KERNCONF=3DGENERICvtsc-NODEBUG TARGET=3Dpowerpc .if ${.MAKE.LEVEL} =3D=3D 0 TARGET_ARCH=3D${TO_TYPE} .export TARGET_ARCH .endif # WITH_FAST_DEPEND=3D WITH_LIBCPLUSPLUS=3D WITH_LIB32=3D WITH_BOOT=3D WITH_CLANG_BOOTSTRAP=3D WITH_CLANG=3D WITH_CLANG_IS_CC=3D WITH_CLANG_FULL=3D WITH_CLANG_EXTRAS=3D # # lldb requires missing atomic 8-byte operations for powerpc (non-64) WITHOUT_LLDB=3D # WITHOUT_GCC_BOOTSTRAP=3D WITHOUT_GCC=3D WITHOUT_GNUCXX=3D # NO_WERROR=3D MALLOC_PRODUCTION=3D # WITHOUT_DEBUG=3D WITHOUT_DEBUG_FILES=3D And GENERICvtsc-NODEBUG being: include GENERIC ident GENERICvtsc nooptions PS3 #Sony Playstation 3 = HACK!!! to allow sc options DDB # HACK!!! to dump early crash = info (but 11.0-CURRENT already has it) options GDB # HACK!!! ... #options VERBOSE_SYSINIT #options BOOTVERBOSE=3D1 #options BOOTHOWTO=3DRB_VERBOSE #options KTR #options KTR_MASK=3DKTR_TRAP #options KTR_CPUMASK=3D0xF #options KTR_VERBOSE # HACK!!! to allow sc for 2560x1440 display on Radeon X1950 that vt = historically mishandled during booting device sc #device kbdmux # HACK: already listed by vt options SC_OFWFB # OFW frame buffer options SC_DFLT_FONT # compile font in makeoptions SC_DFLT_FONT=3Dcp437 # Disable extra checking typically used for FreeBSD 11.0-CURRENT: #nooptions DEADLKRES #Enable the deadlock resolver #nooptions INVARIANTS #Enable calls of extra sanity = checking #nooptions INVARIANT_SUPPORT #Extra sanity checks of internal = structures, required by INVARIANTS #nooptions WITNESS #Enable checks to detect = deadlocks and cycles #nooptions WITNESS_SKIPSPIN #Don't run witness on spinlocks = for speed #nooptions MALLOC_DEBUG_MAXZONES # Separate malloc(9) zones As I'm no where near getting a matching buildkernel to complete I've not = tried to test this buildworld result on a PowerMac that I have access = to. =3D=3D=3D Mark Millard markmi at dsl-only.net