From owner-freebsd-ppc@freebsd.org Sun May 6 21:31:14 2018 Return-Path: Delivered-To: freebsd-ppc@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 D7AE3FC8382 for ; Sun, 6 May 2018 21:31:14 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic303-23.consmr.mail.gq1.yahoo.com (sonic303-23.consmr.mail.gq1.yahoo.com [98.137.64.204]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 62F13843D8 for ; Sun, 6 May 2018 21:31:14 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: LAlKefUVM1mh7DLfBSci.qoUvrxK.pEcGljsyPNSBWCzx9._3WeOfbPAdP3C6ax tz8t9slm2MTJiCLz85lBvi_hsDSwqYmVniZ9RNOZben0Bwsro8jmyPRZXnOwcMdR9pjGj0lF2z0q p5u3aFfb7nuVVrUS7IfCwtK6V6TIosC4o6fogsb2_4yBarz8zIl9Lns3L.mvZNANN1036HeeAOLp l6FToUdZpiGz3ybE.7KNsgTqDwp_H1MRLs_c4NPN.jzcqMH3WI5jYmjcQWb30jbpb0gY3USwu5kf B1GiV2GXadOe4haGyROn6teC5zUAVprtPe5r.2te5CrLJxgBcRDdLMdEQwgW2ImhEoTutffQZOOP D1PC0ma2lIL5lgIC6bQqUh_hJBrkdqqF96WbCw_JB6DyhyaGs.xcdtIkNc8NcCG5ppqqieuFOF7S qaRDR4Xz8xGoulbK1FdzE7MBl89kap2fdGMWmt9y3sFVG3CljmIrhgzhAo2fIQJGS0xccpJMJemK KdeXI0cNfb6A6t09o6JlsN0AHyJqOWait9LSxq4zkEbzugEXh1gEd.yY8nRsDywuomTOlJzp1L9l jWcFc.KUhr35lf11ts1.tbaMgYOwlnGsmS6RIOb1jSBrxxiyNatvSWRq08sJq2gYTb842yLVEODD 8VO6xGWo- Received: from sonic.gate.mail.ne1.yahoo.com by sonic303.consmr.mail.gq1.yahoo.com with HTTP; Sun, 6 May 2018 21:31:07 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.25]) ([76.115.7.162]) by smtp432.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID dbbed42e5a97567b991ef63a5f9f1e3c; Sun, 06 May 2018 21:31:06 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Subject: gcc 8 has declared powerpc*-*-*spe* obsolete, needing --enable-obsolete Message-Id: <276FA8A3-97E4-42A1-9DA3-550E8000B586@yahoo.com> Date: Sun, 6 May 2018 14:31:05 -0700 To: FreeBSD PowerPC ML , freebsd-toolchain@freebsd.org X-Mailer: Apple Mail (2.3445.6.18) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 May 2018 21:31:15 -0000 https://gcc.gnu.org/gcc-8/changes.html reports: =E2=80=A2 Support for the powerpc*-*-*spe* target ports which = have been recently unmaintained and untested in GCC has been declared = obsolete in GCC 8 as announced here. Unless there is activity to revive = them, the next release of GCC will have their sources permanently = removed. Side note: Mixed with clang's powerpc family status for buildworld, such as ignoring __builtin_eh_return so that thrown C++ exceptions will not work for the world so built, powerpc*-*-*spe* looks to have a substantial toolchain problems going forward. =3D=3D=3D Mark Millard marklmi26-fbsd at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-ppc@freebsd.org Sun May 6 22:10:19 2018 Return-Path: Delivered-To: freebsd-ppc@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 62B33FC8EAC; Sun, 6 May 2018 22:10:19 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-lf0-x233.google.com (mail-lf0-x233.google.com [IPv6:2a00:1450:4010:c07::233]) (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 B82926CA97; Sun, 6 May 2018 22:10:18 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: by mail-lf0-x233.google.com with SMTP id u21-v6so37851551lfu.9; Sun, 06 May 2018 15:10:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-transfer-encoding; bh=fc8uYHPGRad8WRTzfOypHzulht61PmMsddvcQfY78o4=; b=UnI/mmaj0oNsfJQvXdLzLwfuCBps6CtKkR/LO+lAE5fdfZDC9PvdJiUVdw08SO7V3T yRKz8TE5HlRMrPAz3/wS7GC0Q+JCHAOjb3oJdhhcPc5a8RQ+d0WpGkgoHFPdd/CiS+dj 3BWsFYIs5Yu/QMo5EulQ4TyNfH1+ZYq1GP5bkuYsqmmP8xm4e0H81XOpHWNLFEA7CbQ/ mNsMTIGGZ3dDZ/9rKEixD824rDp/tTo419MRc7o6m3SYrCks0j5yXPxfS5z3lHQEOndA iBKcj+yLtv5QDcgAWpSsP0yKY3Rksa2gm1aYn9wA/KCa+pPVCjs+PqNXvGbis9Z6KyCm 4BEg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alumni-cwru-edu.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-transfer-encoding; bh=fc8uYHPGRad8WRTzfOypHzulht61PmMsddvcQfY78o4=; b=QUoB2ph45xCN5E1OtvfZLLvZl9aOqnAx6leSfManhSSoixo95DEmxQuaoJizttudju 8nuaT1mkUSJO8ghAT/NA3mzMa6+/5OcQ0N9xKYVKFfD1R1BXWBGZOKKidvXzCPGCJmzZ xHpP8TGD3otlUeCOSm9ddSXI+Kl2XPGaZl2woYD8v9L3lkQ6mkg045SBCWvHQdsqFVxR 90pauozFs4gzaxuD1EGe55hiysQXuXMO9wKzmQd3a/uFXUZJZfPEedewrV0SW6hvN0uh kRlPw0NOseXKPlFWA9v8onKVU5ZAiNPghEbjZ6ocbeJi1afbqybTbPOpa8SOpadESkx4 AaoQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc:content-transfer-encoding; bh=fc8uYHPGRad8WRTzfOypHzulht61PmMsddvcQfY78o4=; b=IpI1bc4OZoCL5sNAb5sfKuBNnYCBKM4XcgSwflo6wQyPudPqve5ois7cEptRf1OCjL Ij773x/cVIDGpSN19/Zc2Y4uyFUGReYLrrQ+foLqLXSfRmzoQwl4/xbv7NHS3mSBO9Ef xX4LuHuVYhXyhUne4OEiVzToXNirurKC6UoexRSq8k2jDrjk7YZOn3kRPFh4Dh3O08Qr EqY80XZoS4Iwxk98oVGqzt59Fom09Lom9kLnZUoekUxJ6F7+OV63OOAKp0Q/j71aMnKQ gQyNawpxAqrcRSKeB9cZ42l4lEBuPpZ2CcdKya49enAVSrLzZ9s88h4bk9C9LAn48iqP VnYw== X-Gm-Message-State: ALQs6tAWDYGyPsY0jSBqUmXaAMENVgYaMKVDKYkWtJFmOzpHoe4HKrYt s6r+chYZPbJDGtCGHJlZ1Ye5PibaZpagrzlzaZc= X-Google-Smtp-Source: AB8JxZrRV4nxcd1FjDdo/jvKdIX6LKzEh43m2z/opqsfd/C2H8N/YDL+YvjWd0gSqRd7ym9/QPqgjcPaOR2GFOr2Lhs= X-Received: by 2002:a19:1303:: with SMTP id j3-v6mr6416490lfi.107.1525644616943; Sun, 06 May 2018 15:10:16 -0700 (PDT) MIME-Version: 1.0 Sender: chmeeedalf@gmail.com Received: by 10.46.58.19 with HTTP; Sun, 6 May 2018 15:10:16 -0700 (PDT) In-Reply-To: <276FA8A3-97E4-42A1-9DA3-550E8000B586@yahoo.com> References: <276FA8A3-97E4-42A1-9DA3-550E8000B586@yahoo.com> From: Justin Hibbits Date: Sun, 6 May 2018 17:10:16 -0500 X-Google-Sender-Auth: SnHleYns-JYN5xHn4JOYnchpzeQ Message-ID: Subject: Re: gcc 8 has declared powerpc*-*-*spe* obsolete, needing --enable-obsolete To: Mark Millard Cc: FreeBSD PowerPC ML , FreeBSD Toolchain Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 May 2018 22:10:19 -0000 Hi Mark, On Sun, May 6, 2018 at 4:31 PM, Mark Millard via freebsd-ppc wrote: > https://gcc.gnu.org/gcc-8/changes.html reports: > > =E2=80=A2 Support for the powerpc*-*-*spe* target ports which hav= e been recently unmaintained and untested in GCC has been declared obsolete= in GCC 8 as announced here. Unless there is activity to revive them, the n= ext release of GCC will have their sources permanently removed. > > > Side note: Mixed with clang's powerpc family status for buildworld, > such as ignoring __builtin_eh_return so that thrown C++ exceptions > will not work for the world so built, powerpc*-*-*spe* looks to > have a substantial toolchain problems going forward. > > =3D=3D=3D > Mark Millard > marklmi26-fbsd at yahoo.com > ( dsl-only.net went > away in early 2018-Mar) I'm aware that gcc8 is deprecating powerpc*spe targets. However, the architecture itself will exist through at least 2025, as chips are guaranteed to be produced until at least that time (part of Freescale/NXP's longevity program). Also, I have some patches in review adding SPE support to LLVM, and will likely be committing them in the next month after I get final reviews and rebase. I'm hoping powerpc support gets enhanced to the point of full support before too long, so we can switch powerpc* targets entirely to clang/llvm. However, we need compiler people who could invest time into doing the work. - Justin From owner-freebsd-ppc@freebsd.org Mon May 7 03:34:19 2018 Return-Path: Delivered-To: freebsd-ppc@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 92F0BFCE4BA for ; Mon, 7 May 2018 03:34:19 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic312-23.consmr.mail.ne1.yahoo.com (sonic312-23.consmr.mail.ne1.yahoo.com [66.163.191.204]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2646C69290 for ; Mon, 7 May 2018 03:34:19 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: pRy7ElcVM1n47eZ30Mzj_4ZwwmfFFWvUTRIENHa5NZ2gehvl4SyGxVwddESFfDs .RrheVufaMUMwJDYC9DUMAAlfSqLR7rLhMWFSychQ88umCZgaLDEz2WPuYYnPePuSWa8the25TaB Qdzuc9UrySZPQ_b_1pyAjFwkGWToQYWmS52V28PsICbtFIhWx5yrYdOwNWTRmRZ84b26eszG6FF6 h.uK0aOWAX2HoQpKlxaWh3dHA_gUvZuDelH0Dp7DuyQlATXszpxN2fCnBvkmBpuqEP6Z_5yZ7mmH HccodZ4sSc1_48QeShlrdzqWhoOljkqxAmSBvJtsyiEGTSl_jfUBcffgG0oWF9_nZASluCmY4ezM zp7xrBUDf7KnkfhiQX_HudzuHuydQrDMDJ.F0DRxc_aE89N76BlCZ1jFD5LL_rAqeDS_xQPtVXo6 vpJppVh0x10dPrLQPs61wZXg3D6M9BXW1zhWkQR_YDL6SjoBHeVOgi9lbzJ8YkC7KaEg5f.r0o9f bNm0huzGekd0g5Xkpp7gn9k1B0Iy_kL2lUycYho_IXrfgpIK4yLMW0.Dy__3HXNb604dD9pGQLum PTSVNKlnUZRVIy3ijfEZuU3bHWkxf0LliTiGBGbr029UwlY9_M7q5fXG20_9k6RAulxx26JLil46 6gF1sb7E- Received: from sonic.gate.mail.ne1.yahoo.com by sonic312.consmr.mail.ne1.yahoo.com with HTTP; Mon, 7 May 2018 03:34:18 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.158]) ([76.115.7.162]) by smtp424.mail.ne1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 65a09db5e9e52ef6b35440b2fc441c41; Mon, 07 May 2018 02:33:36 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Subject: Re: svn commit: r333240 - in head/sys: powerpc/powerpc sys [appears to have broken the builds of head for riscv64] Message-Id: <8E3C5DFF-BC87-4822-9A35-BF206A735EAA@yahoo.com> Date: Sun, 6 May 2018 19:33:34 -0700 To: FreeBSD Current , FreeBSD PowerPC ML X-Mailer: Apple Mail (2.3445.6.18) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 May 2018 03:34:19 -0000 Conrad Meyer cem at freebsd.org wrote on Sun May 6 22:32:13 UTC 2018, as part of a reply: > P.S., Mark, your email server is misconfigured and most/all of your > emails get flagged as spam. I only saw this because I occasionally > check the spam folder. I wrote back directly indicating that I'd need evidence in order to submit something to yahoo.com. Although, the original was not sent directly to Conrad, so he likely got the message directly from a freebsd-current server, with a yahoo.com's Email server as an intermediate stage. (I do not run my own servers.) The Email was composed in macOS's Mail.app [V11.3 (3445.6.18)]. Of course, that reply was likely classified as spam. If anyone else has such problems with the classification of my Emails and can send material that would allow reporting evidence to be submitted someplace, please do so. === Mark Millard marklmi26-fbsd at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-ppc@freebsd.org Mon May 7 19:38:41 2018 Return-Path: Delivered-To: freebsd-ppc@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 9EB89FBAEAC for ; Mon, 7 May 2018 19:38:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 403FC76C71 for ; Mon, 7 May 2018 19:38:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by freefall.freebsd.org (Postfix) id 380491781E; Mon, 7 May 2018 19:38:41 +0000 (UTC) Delivered-To: powerpc@localmail.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by freefall.freebsd.org (Postfix) with ESMTPS id 328161781B for ; Mon, 7 May 2018 19:38:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EB1D176C65 for ; Mon, 7 May 2018 19:38:40 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 29A691BB35 for ; Mon, 7 May 2018 19:38:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w47Jcegi071465 for ; Mon, 7 May 2018 19:38:40 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w47JceMs071464 for powerpc@FreeBSD.org; Mon, 7 May 2018 19:38:40 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: powerpc@FreeBSD.org Subject: [Bug 228055] lang/gcl fails to compile on powerpc64 Date: Mon, 07 May 2018 19:38:40 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new 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: hamiltcl@verizon.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ports-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter cc Message-ID: 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.25 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 May 2018 19:38:42 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D228055 Bug ID: 228055 Summary: lang/gcl fails to compile on powerpc64 Product: Ports & Packages Version: Latest Hardware: powerpc OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: hamiltcl@verizon.net CC: powerpc@FreeBSD.org CC: powerpc@FreeBSD.org Attempting to compile lang/gcl anf gets the following error: ; (IN-PACKAGE 'PCL) is being compiled. ;; Warning: The package operation (IN-PACKAGE 'PCL) was in a bad place. ; (SHADOW 'DOCUMENTATION) is being compiled. ;; Warning: The package operation (SHADOW 'DOCUMENTATION) was in a bad plac= e. End of Pass 1.=20=20 End of Pass 2.=20=20 OPTIMIZE levels: Safety=3D1 (No runtime error checking), Space=3D0, Speed= =3D3 Finished compiling /usr/ports/lang/gcl/work/gcl/unixport/../pcl/gcl_pcl_pkg= .o. Loading binary of GCL_PCL_PKG... Loading /usr/ports/lang/gcl/work/gcl/unixport/../pcl/gcl_pcl_pkg.o Unknown reloc type 10 Error: ERROR "The assertion tp&^tp on line 185 of sfaslelf.c in function relocate failed" Fast links are on: do (si::use-fast-links nil) for debugging Signalled by LOAD. ERROR "The assertion tp&^tp on line 185 of sfaslelf.c in function relocate failed" Broken at LOAD. Type :H for Help. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-ppc@freebsd.org Mon May 7 20:39:34 2018 Return-Path: Delivered-To: freebsd-ppc@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 DED22FBC4B4 for ; Mon, 7 May 2018 20:39:33 +0000 (UTC) (envelope-from andy.silva@snsreports.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 6284C87F5C for ; Mon, 7 May 2018 20:39:33 +0000 (UTC) (envelope-from andy.silva@snsreports.com) X-MSFBL: N2mVypYA+28hzbDbn0eCZbpBiSsBNMc0hye+/8SXZmI=|eyJyIjoiZnJlZWJzZC1 wcGNAZnJlZWJzZC5vcmciLCJnIjoiU25zdGVsZWNvbV9kZWRpY2F0ZWRfcG9vbCI sImIiOiJTbnN0ZWxlY29tX2RlZGljYXRlZF9wb29sXzc0XzkxXzg1XzIzOCJ9 Received: from [10.137.129.35] ([10.137.129.35:44802] helo=mtl-mtsp-c02-3.int.smtp) by mtl-mtsp-mta05-out1.smtp.com (envelope-from ) (ecelerity 4.2.1.55028 r(Core:4.2.1.12)) with ESMTP id D7/BE-11423-FC4B0FA5; Mon, 07 May 2018 20:19:27 +0000 Received: from 10.137.11.94 by Caffeine (mtl-mtsp-c02-3) with SMTP id 3787ed0b-ed3f-477f-aa80-0df67bf81c92 for freebsd-ppc@freebsd.org; Mon, 07 May 2018 20:19:24 +0000 (UTC) Received: from [65.49.242.4] ([65.49.242.4:19526] helo=gull-dhcp-65-49-242-4.bloombb.net) by mtl-mtsp-mta05-in2 (envelope-from ) (ecelerity 4.1.0.46749 r(Core:4.1.0.4)) with ESMTPA id BC/57-02671-CC4B0FA5; Mon, 07 May 2018 20:19:24 +0000 MIME-Version: 1.0 From: "Andy Silva" Reply-To: andy.silva@snsreports.com To: freebsd-ppc@freebsd.org Subject: The Wearable Technology Ecosystem: 2018 - 2030 - Opportunities, Challenges, Strategies, Industry Verticals and Forecasts (Report) X-Mailer: Smart_Send_2_0_138 Date: Mon, 7 May 2018 16:19:22 -0400 Message-ID: <38684376867601405112505@Ankur> Feedback-ID: 6008902:SMTPCOM X-SMTPCOM-Sender-ID: 6008902 X-SMTPCOM-Tracking-Number: 3787ed0b-ed3f-477f-aa80-0df67bf81c92 X-SMTPCOM-Message-ID: 30085833-1227-46b1-802f-f0172c1ff0ed X-SMTPCOM-Payload: =?utf-8?q?AW0Er4IUuvpwo07SQfc4YjJMraxbU0LQrzdAaGg2ZLXV?= =?utf-8?q?hTfMVBKE4jB01K1uWVCHZTPNMfl7QSlO=5FraSwEl2II-qU-Q5jqQzq3KUPybSn?= =?utf-8?q?X3i2xJSlBm7KW5gP-UcEazzNBzlvDoLa8I2YS8bWeqxEA=3D=3D?= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=smtpserver.email; i=@smtpserver.email; q=dns/txt; s=smtpcustomer; t=1525724365; h=MIME-Version : From : Reply-To : To : Subject : Content-Type : Date : Message-ID : List-Unsubscribe : From : Subject : Date; bh=JUqw/z2+6GLzGbw8Xrl3/Eo76JkJbKi+TEIQ7s2Knww=; b=L9FJOnnS2xnymZEZ6aAlJPOFnCl3xqxmvTQmUy54X3jw5G9yRj/z3rfOGvoYpazCkcYE7j UdKORxu4jjptSit9mhjab+OAPPvKn0l3tWmGieDsUJjVAnsi4xs3yqdTVjXGbIvwxIb4JuSc uIt8vz85quAr56sKyfwO1L0zyGYghNNUJSadEIL7mWA1A8VZbet8iqhi/cR/h5sLP5E4ncAJ k5253uWJhLwWQY0L6XJVhpHa36FbnPUIQ3JceF86RlZqgNN7Xa6ReTwjcjVK89pTBanvOu4m Dq/Sh/TY613BX0iBkIJKQT2wbuiIle4Tb3DiuQLn8bvDgcalfW7NmiIw== X-Report-Abuse: SMTP.com is an email service provider. Our abuse team cares about your feedback. Please contact abuse@smtp.com for further investigation. Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 May 2018 20:39:34 -0000 The Wearable Technology Ecosystem: 2018 =96 2030 =96 Opportunities, Challen= ges, Strategies, Industry Verticals and Forecasts (Report) Hello Let me offer you the latest SNS Research report to you and your team, "The = Wearable Technology Ecosystem: 2018 =96 2030 =96 Opportunities, Challenges,= Strategies, Industry Verticals and Forecasts" Below is the report highligh= t and if you like I can send you sample pages for your details inside.=20 While wearable technology has been utilized in vertical sectors such as the= military and healthcare industries for many years, ongoing advances have t= riggered a major resurgence of the concept, particularly among the consumer= community. Key enabling technologies including low cost sensors, wireless = connectivity, active materials and energy have converged to make wearable t= echnology mainstream. Driven by the ability to interconnect with key modern trends of healthcare,= fitness, messaging and socialization, the wearable technology ecosystem is= attracting significant levels of interest. Companies as varied as smartph= one OEMs, mobile operators, health insurers and retailers are circling the = ecosystem alongside tiny startups, all vying for a stake. SNS Telecom & IT estimates that wearable device shipments will grow at a CA= GR of approximately 22% between 2018 and 2021. By the end of 2021, wearable= devices will represent a market worth $45 Billion with over 250 Million an= nual unit shipments. The =93Wearable Technology Ecosystem: 2018 =96 2030 =96 Opportunities, Chal= lenges, Strategies, Industry Verticals & Forecasts=94 report presents an in= -depth assessment of the wearable technology ecosystem including market dri= vers, challenges, enabling technologies, consumer and enterprise applicatio= ns, key trends, case studies, opportunities, future roadmap, value chain, e= cosystem player profiles, vendor market share and strategies. The report al= so presents forecasts for wearable device shipments and revenue from 2018 t= hrough to 2030. The forecasts cover 9 device form factor submarkets, 7 vert= ical markets, 6 regions and 73 countries. Report Information: Release Date: April 2018 Number of Pages: 596 Number of Tables and Figures: 230 Key Questions Answered: How big is the wearable technology ecosystem=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 2021 and at what rate will it grow=3F Which vertical markets will see the highest percentage of growth=3F How do standardization and regulation impact the adoption of wearable techn= ology for the healthcare industry and other sectors=3F What opportunities exist for cellular chipset suppliers in the wearable tec= hnology ecosystem=3F How can mobile operators capitalize on the growing popularity of smartwatch= es, fitness bands, smart glasses and other wearable devices=3F What are the future prospects of hearables and other emerging form factors=3F Who are the key ecosystem players and what are their strategies=3F What strategies should wearable technology suppliers and vertical domain sp= ecialists adopt to remain competitive=3F Key Findings: The report has the following key findings: SNS Telecom & IT estimates that wearable device shipments will grow at a CA= GR of approximately 22% between 2018 and 2021. By the end of 2021, wearable= devices will represent a market worth $45 Billion with over 250 Million an= nual unit shipments. In terms of annual wearable device unit shipments, the top 5 vendors =96 A= pple, Xiamo, Fitbit, Samsung and Garmin =96 collectively account for more t= han 55% of the market. Cellular connectivity and associated advanced capabilities =96 such as VoLT= E (Voice over LTE) =96 are increasingly being integrated into consumer orie= nted wearables such as smartwatches. SNS Telecom & IT estimates that wearable devices will help mobile operators= drive more than $12 Billion in service revenue by the end of 2021, followi= ng a CAGR of approximately 36% between 2018 and 2021. As wearable technology vendors seek to minimize dependence on hardware sale= s, new business models are continuing to gain popularity =96 ranging from c= orporate wellness programs to sports performance analytics. The report covers the following topics: Wearable technology ecosystem Market drivers and barriers Key enabling technologies and concepts including low cost sensors, wirele= ss connectivity, voice recognition and augmented reality Analysis of vertical markets and applications =96 for consumer, healthcare,= professional sports, retail & hospitality, military, public safety and 8 o= ther sectors Case studies of 10 wearable technology deployments =96 reviewing solutions,= vendors, applications and feedback from end users Wearable device vendor market share Prospects of smartphone OEMs and cellular chipset suppliers in the wearable= technology ecosystem Impact of 5G NR (New Radio), cellular IoT and ProSe (Proximity Services) on= wearable technology Industry roadmap and value chain Profiles and strategies of more than 360 leading ecosystem players includin= g wearable technology suppliers and vertical domain specialists Strategic recommendations for enabling technology providers, wearable devic= e OEMs, application developers and mobile operators Market analysis and forecasts from 2018 till 2030 Forecast Segmentation: VoLTE subscription, service revenue and infrastructure revenue forecasts ar= e provided for each of the following submarkets and their subcategories: Form Factor Submarkets Smart Bands Smartwatches OS-Powered Smartwatches Basic Smartwatches Smart Glasses Smart Clothing Smart Earwear Smart Jewelry Heads-up Displays Others Vertical Submarkets Consumer Healthcare Professional Sports Retail & Hospitality Military Public Safety Others Regional Markets Asia Pacific Eastern Europe Latin & Central America Middle East & Africa North America Western Europe Country Markets 73 Country level markets: Algeria, Argentina, Australia, Austria, Banglades= h, Belarus, Belgium, Bolivia, Bosnia & Herzegovina, Brazil, Bulgaria, Canad= a, Chile, China, Colombia, Croatia, Czech Republic, Denmark, Ecuador, Egypt= , Finland, France, Germany, Greece, Hong Kong, Hungary, India, Indonesia, I= reland, Israel, Italy, Japan, Kenya, Luxembourg, Malaysia, Mexico, Morocco,= Netherlands, New Zealand, Nigeria, Norway, Pakistan, Paraguay, Peru, Phili= ppines, Poland, Portugal, Qatar, Romania, Russia, Saudi Arabia, Serbia, Sin= gapore, Slovakia, South Africa, South Korea, Spain, Sudan, Sweden, Switzerl= and, Taiwan, Tanzania, Thailand, Tunisia, Turkey, UAE, UK, Ukraine, Uruguay= , USA, Uzbekistan, Venezuela and Vietnam Report Pricing: =20 Single User License: USD 2,500 Company Wide License: USD 3,500 =20 Ordering Process: =20 Please provide the following information: Report Title - Report License - (Single User/Company Wide) Name - Email - Job Title - Company - 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 in report are given below for= more inside. I look forward to hearing from you. =20 Kind Regards =20 Andy Silva Marketing Executive Signals and Systems Telecom =20 _________________________________________________________________________ Table of Contents: =20 1 Chapter 1: Chapter 1: Introduction 1.1 Executive Summary 1.2 Topics Covered 1.3 Forecast Segmentation 1.4 Key Questions Answered 1.5 Key Findings 1.6 Methodology 1.7 Target Audience 1.8 Companies & Organizations Mentioned =20 2 Chapter 2: An Overview of Wearable Technology 2.1 What is Wearable Technology=3F 2.2 Device Classification 2.2.1 Head-Worn Devices 2.2.2 Wrist-Worn Devices 2.2.3 Leg and Ankle-Worn Devices 2.2.4 Arm, Chest and Neck-Worn Devices 2.2.5 Smart Clothing & Jewelry 2.2.6 In-Body Wearables 2.3 Enabling Technologies 2.3.1 MEMS & Sensors 2.3.2 BT-LE (Bluetooth Low Energy) & Wi-Fi 2.3.3 Voice Recognition 2.3.4 Lowed Powered Wireless SoCs 2.3.5 RFID & NFC 2.3.6 GPS & Navigation Technology 2.3.7 Energy Harvesting 2.3.8 Ergonomics & Materials Science 2.3.9 Augmented Reality 2.4 Market Growth Drivers 2.4.1 Proliferation of Smartphones 2.4.2 Advances in Enabling Technologies & Components 2.4.3 Interest from New Market Segments 2.4.4 Human Centric Assistance 2.4.5 Meaningful Analytics & Tracking 2.4.6 Venture Capital, Crowdfunding & Corporate Investments 2.4.7 Endorsement by Major Mobile OEMs 2.5 Market Barriers 2.5.1 High Costs 2.5.2 Power Consumption & Battery Life Issues 2.5.3 Usability & Unusual Styling 2.5.4 Potential Health Issues 2.5.5 Privacy & Security Concerns 2.5.6 Social Acceptance 3 Chapter 3: Vertical Opportunities & Use Cases 3.1 Consumer Markets 3.1.1 Infotainment & Lifestyle 3.1.1.1 Personal Assistance, Notifications & Alerts 3.1.1.2 Photography 3.1.1.3 Navigation Assistance 3.1.1.4 Smart Home Applications 3.1.1.5 Media & Entertainment 3.1.1.6 Memory Recall 3.1.2 Casual Sports & Fitness 3.1.3 Contactless Payments 3.1.4 Gaming 3.1.5 Pet Care 3.1.6 Child Care & Entertainment 3.1.7 Helping People with Disabilities 3.1.8 Car Insurance Claims 3.1.9 Accurate & Targeted Marketing 3.2 Healthcare 3.2.1 Remote Patient Monitoring 3.2.2 Assisted Patient Examination 3.2.3 Reducing Healthcare Costs 3.2.4 Optimizing Health Insurance Costs 3.2.5 Enhancing Medical R&D 3.3 Professional Sports 3.3.1 Sports Data Analytics 3.3.2 Enhancing Real-Time Decision Making 3.3.3 Injury Prevention 3.4 Retail & Hospitality 3.4.1 Improving Retail Productivity 3.4.2 Comparing & Contrasting Retail Items 3.4.3 Travel: Personalizing Customer Service 3.4.4 Replacing Hotel Keys and Credit Cards 3.4.5 Augmenting City & Museum Tours 3.5 Military 3.5.1 Enhancing Infantry Tactics: Shooting Without Being Shot 3.5.2 Monitoring Combat Stress & Injuries 3.5.3 Enhancing Situational Awareness in the Battlefield 3.5.4 Enabling Battlefield Mobility 3.5.5 Facilitating Communications with Military Dogs 3.6 Public Safety 3.6.1 Recording Criminal Evidence 3.6.2 Enhancing Situational Awareness & Assets Coordination 3.6.3 Identifying Suspects & Traffic Violators 3.6.4 Monitoring Biophysical Activity for First Responders 3.6.5 Enhancing Fire Fighting Capabilities 3.6.6 Improving Response to Medical Emergencies 3.7 Other Verticals 3.7.1 Construction Industry 3.7.2 Mining Industry 3.7.3 Manufacturing Operations 3.7.4 Logistics & Supply Chain 3.7.5 Financial Services 3.7.6 Security & Authentication 3.7.7 Repair, Inspection & Field Services 3.7.8 Education 3.8 Case Studies 3.8.1 Appirio: Cutting Health Insurance Costs with Fitbit 3.8.1.1 Solution & Vendors 3.8.1.2 Applications 3.8.1.3 Feedback from the Field 3.8.2 AT&T: Connected Healthcare Monitoring for the Elderly 3.8.2.1 Solution & Vendors 3.8.2.2 Applications 3.8.2.3 Feedback from the Field 3.8.3 DHL: Implementing Vision Picking with Smart Glasses 3.8.3.1 Solution & Vendors 3.8.3.2 Applications 3.8.3.3 Feedback from the Field 3.8.4 Dubai Police: Catching Speeding Drivers with Google Glass 3.8.4.1 Solution & Vendors 3.8.4.2 Applications 3.8.4.3 Feedback from the Field 3.8.5 Florida State University: Reducing Sports Injuries with Wearable Perf= ormance Tracking 3.8.5.1 Solution & Vendors 3.8.5.2 Applications 3.8.5.3 Feedback from the Field 3.8.6 KDDI Corporation: Ensuring Child Safety with Smartwatches 3.8.6.1 Solution & Vendors 3.8.6.2 Applications 3.8.6.3 Feedback from the Field 3.8.7 Medisafe: Improving Medication Adherence with Wearable Technology 3.8.7.1 Solution & Vendors 3.8.7.2 Applications 3.8.7.3 Feedback from the Field 3.8.8 The Walt Disney Company: Theme Park Management with Wearable Technolo= gy 3.8.8.1 Solution & Vendors 3.8.8.2 Applications 3.8.8.3 Feedback from the Field 3.8.9 U.S. Department of Defense: Delivering Tactical Information with Wear= able Display Systems 3.8.9.1 Solution & Vendors 3.8.9.2 Applications 3.8.9.3 Feedback from the Field 3.8.10 Virgin Atlantic Airways: Enhancing Airline Services with Wearable Te= chnology 3.8.10.1 Solution & Vendors 3.8.10.2 Applications 3.8.10.3 Feedback from the Field =20 4 Chapter 4: Industry Roadmap & Value Chain 4.1 Wearable Technology Industry Roadmap 4.1.1 Pre-2020: Growing Proliferation of Wearables & Emerging Business Mode= ls 4.1.2 2020 =96 2025: Increasing Focus on Enterprise Markets & Use Cases 4.1.3 2025 =96 2030: Growth in Mobile Operator Service Revenues 4.2 The Wearable Technology Value Chain 4.2.1 Enabling Technology Ecosystem 4.2.1.1 Chipset Vendors 4.2.1.2 Sensor, Display & Enabling Hardware Providers 4.2.1.3 OS & Software Providers 4.2.1 Wearable Device OEM Ecosystem 4.2.1.1 Vertical Centric OEMs 4.2.1.2 Smartphone, Tablet & Consumer Electronics OEMs 4.2.1.3 Fashion & Watch OEMs 4.2.2 Consumers & Vertical Enterprises 4.2.3 Mobile Operators & the Connectivity Ecosystem 4.2.4 Applications Ecosystem =20 5 Chapter 5: Market Sizing & Forecasts 5.1 Global Outlook for Wearable Technology 5.2 Form Factor Segmentation 5.3 Smart Bands 5.4 Smartwatches 5.4.1 OS-Powered Smartwatches 5.4.2 Basic Smartwatches 5.5 Smart Glasses 5.6 Smart Clothing 5.7 Smart Earwear 5.8 Smart Jewelry 5.9 Heads-up Display Systems 5.10 Others 5.11 Vertical Market Segmentation 5.12 Consumer Wearable Devices 5.13 Healthcare Wearable Devices 5.14 Professional Sports Wearable Devices 5.15 Retail & Hospitality Wearable Devices 5.16 Military Wearable Devices 5.17 Public Safety Wearable Devices 5.18 Wearable Devices in Other Verticals 5.19 Regional Market Segmentation 5.20 Asia Pacific 5.20.1 Australia 5.20.2 Bangladesh 5.20.3 China 5.20.4 Hong Kong 5.20.5 India 5.20.6 Indonesia 5.20.7 Japan 5.20.8 Malaysia 5.20.9 New Zealand 5.20.10 Pakistan 5.20.11 Philippines 5.20.12 Singapore 5.20.13 South Korea 5.20.14 Taiwan 5.20.15 Thailand 5.20.16 Vietnam 5.20.17 Rest of Asia Pacific 5.21 North America 5.21.1 Canada 5.21.2 USA 5.22 Western Europe 5.22.1 Austria 5.22.2 Belgium 5.22.3 Denmark 5.22.4 Finland 5.22.5 France 5.22.6 Germany 5.22.7 Greece 5.22.8 Ireland 5.22.9 Italy 5.22.10 Luxembourg 5.22.11 Netherlands 5.22.12 Norway 5.22.13 Portugal 5.22.14 Spain 5.22.15 Sweden 5.22.16 Switzerland 5.22.17 Turkey 5.22.18 UK 5.22.19 Rest of Western Europe 5.23 Eastern Europe 5.23.1 Belarus 5.23.2 Bosnia & Herzegovina 5.23.3 Bulgaria 5.23.4 Croatia 5.23.5 Czech Republic 5.23.6 Hungary 5.23.7 Poland 5.23.8 Romania 5.23.9 Russia 5.23.10 Serbia 5.23.11 Slovakia 5.23.12 Ukraine 5.23.13 Uzbekistan 5.23.14 Rest of Eastern Europe 5.24 Middle East & Africa 5.24.1 Algeria 5.24.2 Egypt 5.24.3 Israel 5.24.4 Kenya 5.24.5 Morocco 5.24.6 Nigeria 5.24.7 Qatar 5.24.8 Saudi Arabia 5.24.9 South Africa 5.24.10 Sudan 5.24.11 Tanzania 5.24.12 Tunisia 5.24.13 UAE 5.24.14 Rest of the Middle East & Africa 5.25 Latin & Central America 5.25.1 Argentina 5.25.2 Bolivia 5.25.3 Brazil 5.25.4 Chile 5.25.5 Colombia 5.25.6 Ecuador 5.25.7 Mexico 5.25.8 Paraguay 5.25.9 Peru 5.25.10 Uruguay 5.25.11 Venezuela 5.25.12 Rest of Latin & Central America =20 6 Chapter 6: Key Ecosystem Players 6.1 270 Vision 6.2 3L Labs 6.3 4DForce 6.4 4iii Innovations 6.5 9Solutions 6.6 Abbot Laboratories 6.7 Acer 6.8 AcousticSheep 6.9 Active Mind Technology 6.10 Adidas 6.11 AGPtek 6.12 AliveCor 6.13 Amazon 6.14 Amber Alert GPS 6.15 Ambit Networks 6.16 AMD (Advanced Micro Devices) 6.17 AngelSense 6.18 Aplus 6.19 Apple 6.20 ARA (Applied Research Associates) 6.21 Archos 6.22 ARM Holdings 6.23 Arrow Technologies 6.24 Arubixs 6.25 ASUS (ASUSTeK Computer) 6.26 Atellani 6.27 Atheer Labs 6.28 Atlas Wearables 6.29 Augmendix 6.30 Avegant 6.31 AVG 6.32 Axon 6.33 BAE Systems 6.34 Baidu 6.35 BBK Electronics Corporation/OPPO/Vivo 6.36 Beddit 6.37 Behavioral Technology Group 6.38 Bellabeat 6.39 BI (GEO Group) 6.40 Biosensics 6.41 Bitbanger Labs 6.42 Blocks Wearables 6.43 Bmorn 6.44 bOMDIC 6.45 Bondara (Nagook) 6.46 Boston Scientific Corporation 6.47 BRAGI 6.48 Breitling 6.49 Brother Industries 6.50 BSX Athletics 6.51 BTS Bioengineering 6.52 Bulgari 6.53 Caeden 6.54 Casio 6.55 Catapult Sports 6.56 Chronos Wearables 6.57 Citizen 6.58 Cityzen Sciences 6.59 Codoon 6.60 CommandWear 6.61 CompeGPS 6.62 Connect America 6.63 ConnecteDevice 6.64 Cooey 6.65 Cool Shirt Systems 6.66 Cordon 6.67 Creoir 6.68 Cyberdyne 6.69 Cypress Semiconductor Corporation 6.70 DAQRI 6.71 Dell 6.72 Dexcom 6.73 Dialog Semiconductor 6.74 DIGICare Technology 6.75 Digitsole 6.76 DK Tek Innovations 6.77 Doki Technologies 6.78 DorsaVi 6.79 Ducere 6.80 Ekso Bionics 6.81 Electric Foxy 6.82 Emotiv Systems 6.83 Empatica 6.84 Enjoy S.R.L 6.85 Epson (Seiko Epson Corporation) 6.86 EuroTech 6.87 Evena Medical 6.88 Exelis/Harris Corporation 6.89 EyeTap 6.90 FashionTEQ 6.91 Fat Shark 6.92 Fatigue Science 6.93 Finis 6.94 FitBark 6.95 Fitbit 6.96 Flex 6.97 Force Impact Technologies 6.98 Fossil Group /Misfit 6.99 FOVE 6.100 Fujitsu 6.101 Garmin 6.102 GEAK (Shanda Group) 6.103 Gemalto/Thales 6.104 General Dynamics Mission Systems 6.105 Ginger.io 6.106 GlassUp 6.107 Glofaster 6.108 GN Store Nord 6.109 Google/Alphabet 6.110 GoPro 6.111 GOQii 6.112 Guess 6.113 HealBe 6.114 HereO 6.115 Hexoskin (Carre Technologies) 6.116 Hollywog 6.117 Honeywell International 6.118 Hovding 6.119 HP 6.120 HTC Corporation 6.121 Huami 6.122 Huawei 6.123 iBerry 6.124 ICEdot 6.125 ICON Health and Fitness 6.126 iHealth Labs 6.127 iLOC Technologies 6.128 Imagination Technologies 6.129 Imec International 6.130 Immerz 6.131 IMU (I Measure U) 6.132 Ineda Systems 6.133 Innovega 6.134 Instabeat 6.135 Intel Corporation 6.136 InteraXon 6.137 Intex Technologies 6.138 InvenSense 6.139 Iotera 6.140 iRhythm Technologies 6.141 Iron Will Innovations 6.142 Jaguar Land Rover 6.143 Jaybird 6.144 JINS (JIN CO.) 6.145 Johnson & Johnson 6.146 Joyray Technology 6.147 Kairos Watches 6.148 Kerv Wearables 6.149 Ki Performance Lifestyle 6.150 Kiwi Wearable Technologies 6.151 KMS Solutions 6.152 Kokoon 6.153 Kopin Corporation 6.154 KoruLab 6.155 Kronoz 6.156 Kuaiwear 6.157 L3 Technologies 6.158 Laster Technologies 6.159 Le Vise Products 6.160 Leaf Healthcare 6.161 LeapFrog Enterprises/VTech 6.162 Lenovo/Motorola Mobility 6.163 Lepow 6.164 Levi Strauss & Co. 6.165 LG Electronics 6.166 LifeBEAM 6.167 LifeLogger Technologies Corporation 6.168 Limmex 6.169 Lineable 6.170 Linkitz 6.171 Liquid Image 6.172 Livall 6.173 Lockheed Martin Corporation 6.174 LOSTnFOUND 6.175 Lumafit 6.176 Lumo BodyTech 6.177 Lumos 6.178 Lumus 6.179 Luxottica 6.180 Lycos 6.181 Lyle & Scott 6.182 Mad Apparel 6.183 Magellan (MiTAC Digital Corporation) 6.184 MainTool 6.185 Martian Watches 6.186 Matilde 6.187 Mattel 6.188 MC10 6.189 McLear 6.190 MediaTek 6.191 Medtronic 6.192 Merge Labs 6.193 META 6.194 Microsoft Corporation 6.195 Mio Global 6.196 Moff 6.197 Mondaine Watch 6.198 Mondevices 6.199 Montblanc 6.200 Moov 6.201 Moticon 6.202 Motion Fitness 6.203 Mozilla Corporation 6.204 Mutualink 6.205 Myontec 6.206 Neptune 6.207 NeuroPro 6.208 NeuroSky 6.209 New Balance 6.210 Nike 6.211 Nixie Labs 6.212 Nixon 6.213 Nokia 6.214 Nortek Security & Control 6.215 Notch Interfaces 6.216 Now Computing 6.217 NTT DoCoMo 6.218 Nuance Communications 6.219 Nuubo 6.220 NVIDIACorporation 6.221 NXP Semiconductors 6.222 Nymi 6.223 NZN Labs 6.224 OAXIS 6.225 Oculus VR/Facebook 6.226 ODG (Osterhout Design Group) 6.227 Omate 6.228 Omron Corporation 6.229 OMsignal 6.230 Opening Ceremony 6.231 Optalert 6.232 Optinvent 6.233 OrCam Technologies 6.234 OriginGPS 6.235 Orion Labs 6.236 Orpyx Medical Technologies 6.237 O-Synce 6.238 OURA 6.239 Owlet Baby Care 6.240 Panasonic Corporation 6.241 Perceptive Devices 6.242 Perpetua Power Source Technologies 6.243 PFO Tech 6.244 PHTL (PH Technical Labs) 6.245 Pivothead 6.246 Pixie Scientific 6.247 Plantronics 6.248 PNI Sensor 6.249 Polar Electro 6.250 Preventice Solutions 6.251 Proteus Digital Health 6.252 Pulse 6.253 PUSH 6.254 Qardio 6.255 Qualcomm 6.256 Ralph Lauren 6.257 Raytheon Company 6.258 Razer 6.259 Recon Instruments 6.260 Reebok International 6.261 Reemo 6.262 Rest Devices 6.263 ReVault 6.264 Revolutionary Tracker 6.265 Ringly 6.266 Rooti Labs 6.267 RSL Steeper Group 6.268 Rufus Labs 6.269 S3 ID 6.270 Safelet 6.271 Salesforce.com 6.272 Salutron 6.273 Samsung Electronics 6.274 Sarvint Technologies 6.275 Seiko Holdings Corporation 6.276 SenseGiz Technologies 6.277 Sensiia 6.278 Senso Solutions 6.279 Sensoplex 6.280 Sensoria 6.281 Sentimoto 6.282 Shenzen Smart Co. 6.283 Shenzhen Glory Union Electronic Company 6.284 ShiftWear 6.285 Shimmer 6.286 ShotTracker 6.287 Si14 6.288 SIGMA-ELEKTRO 6.289 Simple Matters 6.290 SmartCap Technologies (EdanSafe) 6.291 SMI (SensoMotoric Instruments) 6.292 SMS Audio 6.293 Snap (Formerly Snapchat) 6.294 Snowpow (Shenzhen Snopow Outdoor Technology) 6.295 Somaxis 6.296 Sony Corporation 6.297 Sotera Wireless 6.298 Soundbrenner 6.299 Spice Mobiles 6.300 Spire 6.301 SpotNSave 6.302 Spree Wearables 6.303 Sproutling/Fisher-Price/Mattel 6.304 Sqord 6.305 Stalker Radar (Applied Concepts) 6.306 Starbreeze Studios 6.307 STATSports 6.308 STMicroelectronics 6.309 Striiv 6.310 Sunbeam Products/Newell Rubbermaid 6.311 Suunto 6.312 Swatch Group 6.313 T.Ware 6.314 Tag Heuer 6.315 TCL Communication 6.316 Thalmic Labs 6.317 Theatro 6.318 Thimble Bioelectronics 6.319 TI (Texas Instruments) 6.320 Timex Group 6.321 TLink Golf 6.322 TN Games 6.323 Tobii Group 6.324 TomTom 6.325 Touch Bionics 6.326 TrackingPoint 6.327 Trivoly Technology 6.328 Ubimax 6.329 U-blox 6.330 Under Armour 6.331 Valencell 6.332 Validic (Motivation Science) 6.333 Vancive Medical Technologies (Avery Dennison Corporation) 6.334 Vigo 6.335 VSN Mobil 6.336 Vuzix 6.337 Wahoo Fitness 6.338 Wavelet Health 6.339 Wearable X 6.340 Weartrons Labs 6.341 Weenect 6.342 Wellograph 6.343 Whereables B.V. 6.344 Whistle Labs 6.345 Whoop 6.346 WorldSIM 6.347 WTS (Wonder Technology Solutions) 6.348 Xdream (TickTalk) 6.349 Xensr 6.350 Xiaomi 6.351 Xmetrics 6.352 XOEye Technologies 6.353 Xybermind 6.354 Yingqu Technology 6.355 Yost Labs 6.356 Zackees 6.357 Zebra Technologies 6.358 ZEISS 6.359 Zephyr Technology Corporation 6.360 Zepp Labs 6.361 ZGPax (Shenzhen PGD Digital Technology) 6.362 Zoll Medical Corporation 6.363 ZTE =20 7 Chapter 7: Conclusion, Key Trends & Strategic Recommendations 7.1 Why is the Market Poised to Grow=3F 7.2 Competitive Industry Landscape: Acquisitions, Alliances & Consolidation 7.3 Vendor Share: Who Leads the Market=3F 7.4 Prospects of Smartphone OEMs in the Wearable Technology Ecosystem 7.5 Wearable Technology Operating Systems: Is there a Dominant Market Leade= r=3F 7.6 How is Wearable Technology Affecting the Cellular Chipsets Ecosystem=3F 7.7 5G NR (New Radio), Cellular IoT & ProSe (Proximity Services): Impact on= Wearables 7.8 Mobile Operators: The Service Revenue Opportunity 7.9 Standardization & Regulation 7.10 Combining Fashion with Technology 7.11 Emergence of New Form Factors: From Hearables to Ingestibles 7.12 How Big is the Wearable Applications Ecosystem=3F 7.13 Moving Towards New Applications & Business Models 7.13.1 Healthcare Monitoring & Wellness Programs 7.13.2 Sports Performance Analytics 7.13.3 Smart Home Management 7.13.4 Child Safety & Entertainment 7.13.5 Other Application Areas 7.14 Prospects of Fitness & Sports Centric Wearables 7.15 Recommendations 7.15.1 Enabling Technology Providers 7.15.2 Wearable Device OEMs & Vertical Players 7.15.3 Wearable Application Developers 7.15.4 Mobile Operators =20 List of Figures: =20 Figure 1: In-Body Pill Camera Figure 2: KOR-FX Haptic Feedback Vest Figure 3: DARPA's ULTRA-VIS Wearable Display Unit and Augmented Reality View Figure 4: AT&T's EverThere Wearable Device Figure 5: Summary of DHL's Vision Picking Pilot Figure 6: Catapult OptimEye S5 Athlete Tracking Technology Figure 7: KDDI's mamorino Watch for Children Figure 8: Medisafe App on a Smartwatch Figure 9: Key Functional Capabilities of Disney's MagicBand Figure 10: U.S. Army's TAR (Tactical Augmented Reality) System View Figure 11: Wearable Devices for Virgin Atlantic's Concierge & Engineering S= taff Figure 12: Wearable Technology Industry Roadmap Figure 13: Wearable Technology Value Chain Figure 14: Global Wearable Device Shipments: 2018 =96 2030 (Millions of Uni= ts) Figure 15: Global Wearable Device Shipment Revenue: 2018 =96 2030 ($ Millio= n) Figure 16: Global Wearable Device Shipments by Form Factor: 2018 =96 2030 (= Millions of Units) Figure 17: Global Wearable Device Shipment Revenue by Form Factor: 2018 =96= 2030 ($ Million) Figure 18: Global Smart Band Shipments: 2018 =96 2030 (Millions of Units) Figure 19: Global Smart Band Shipment Revenue: 2018 =96 2030 ($ Million) Figure 20: Global OS-Powered Smartwatch Shipments: 2018 =96 2030 (Millions = of Units) Figure 21: Global OS-Powered Smartwatch Shipment Revenue: 2018 =96 2030 ($ = Million) Figure 22: Global Basic Smartwatch Shipments: 2018 =96 2030 (Millions of Un= its) Figure 23: Global Basic Smartwatch Shipment Revenue: 2018 =96 2030 ($ Milli= on) Figure 24: Global Smart Glasses Shipments: 2018 =96 2030 (Millions of Units) Figure 25: Global Smart Glasses Shipment Revenue: 2018 =96 2030 ($ Million) Figure 26: Global Smart Clothing Shipments: 2018 =96 2030 (Millions of Unit= s) Figure 27: Global Smart Clothing Shipment Revenue: 2018 =96 2030 ($ Million) Figure 28: Global Smart Earwear Shipments: 2018 =96 2030 (Millions of Units) Figure 29: Global Smart Earwear Shipment Revenue: 2018 =96 2030 ($ Million) Figure 30: Global Smart Jewelry Shipments: 2018 =96 2030 (Millions of Units) Figure 31: Global Smart Jewelry Shipment Revenue: 2018 =96 2030 ($ Million) Figure 32: Global Heads-up Display System Shipments: 2018 =96 2030 (Million= s of Units) Figure 33: Global Heads-up Display System Shipment Revenue: 2018 =96 2030 (= $ Million) Figure 34: Global Other Wearable Device Shipments: 2018 =96 2030 (Millions = of Units) Figure 35: Global Other Wearable Device Shipment Revenue: 2018 =96 2030 ($ = Million) Figure 36: Global Wearable Device Shipments by Vertical: 2018 =96 2030 (Mil= lions of Units) Figure 37: Global Wearable Device Shipment Revenue by Vertical: 2018 =96 20= 30 ($ Million) Figure 38: Global Consumer Wearable Device Shipments: 2018 =96 2030 (Millio= ns of Units) Figure 39: Global Consumer Wearable Device Shipment Revenue: 2018 =96 2030 = ($ Million) Figure 40: Global Healthcare Wearable Device Shipments: 2018 =96 2030 (Mill= ions of Units) Figure 41: Global Healthcare Wearable Device Shipment Revenue: 2018 =96 203= 0 ($ Million) Figure 42: Global Professional Sports Wearable Device Shipments: 2018 =96 2= 030 (Millions of Units) Figure 43: Global Professional Sports Wearable Device Shipment Revenue: 201= 8 =96 2030 ($ Million) Figure 44: Global Retail & Hospitality Wearable Device Shipments: 2018 =96 = 2030 (Millions of Units) Figure 45: Global Retail & Hospitality Wearable Device Shipment Revenue: 20= 18 =96 2030 ($ Million) Figure 46: Global Military Wearable Device Shipments: 2018 =96 2030 (Millio= ns of Units) Figure 47: Global Military Wearable Device Shipment Revenue: 2018 =96 2030 = ($ Million) Figure 48: Global Public Safety Wearable Device Shipments: 2018 =96 2030 (M= illions of Units) Figure 49: Global Public Safety Wearable Device Shipment Revenue: 2018 =96 = 2030 ($ Million) Figure 50: Global Wearable Device Shipments in Other Verticals: 2018 =96 20= 30 (Millions of Units) Figure 51: Global Wearable Device Shipment Revenue in Other Verticals: 2018= =96 2030 ($ Million) Figure 52: Wearable Device Shipments by Region: 2018 =96 2030 (Millions of = Units) Figure 53: Wearable Device Shipment Revenue by Region: 2018 =96 2030 ($ Mil= lion) Figure 54: Asia Pacific Wearable Device Shipments: 2018 =96 2030 (Millions = of Units) Figure 55: Asia Pacific Wearable Device Shipment Revenue: 2018 =96 2030 ($ = Million) Figure 56: Australia Wearable Device Shipments: 2018 =96 2030 (Millions of = Units) Figure 57: Australia Wearable Device Shipment Revenue: 2018 =96 2030 ($ Mil= lion) Figure 58: Bangladesh Wearable Device Shipments: 2018 =96 2030 (Millions of= Units) Figure 59: Bangladesh Wearable Device Shipment Revenue: 2018 =96 2030 ($ Mi= llion) Figure 60: China Wearable Device Shipments: 2018 =96 2030 (Millions of Unit= s) Figure 61: China Wearable Device Shipment Revenue: 2018 =96 2030 ($ Million) Figure 62: Hong Kong Wearable Device Shipments: 2018 =96 2030 (Millions of = Units) Figure 63: Hong Kong Wearable Device Shipment Revenue: 2018 =96 2030 ($ Mil= lion) Figure 64: India Wearable Device Shipments: 2018 =96 2030 (Millions of Unit= s) Figure 65: India Wearable Device Shipment Revenue: 2018 =96 2030 ($ Million) Figure 66: Indonesia Wearable Device Shipments: 2018 =96 2030 (Millions of = Units) Figure 67: Indonesia Wearable Device Shipment Revenue: 2018 =96 2030 ($ Mil= lion) Figure 68: Japan Wearable Device Shipments: 2018 =96 2030 (Millions of Unit= s) Figure 69: Japan Wearable Device Shipment Revenue: 2018 =96 2030 ($ Million) Figure 70: Malaysia Wearable Device Shipments: 2018 =96 2030 (Millions of U= nits) Figure 71: Malaysia Wearable Device Shipment Revenue: 2018 =96 2030 ($ Mill= ion) Figure 72: New Zealand Wearable Device Shipments: 2018 =96 2030 (Millions o= f Units) Figure 73: New Zealand Wearable Device Shipment Revenue: 2018 =96 2030 ($ M= illion) Figure 74: Pakistan Wearable Device Shipments: 2018 =96 2030 (Millions of U= nits) Figure 75: Pakistan Wearable Device Shipment Revenue: 2018 =96 2030 ($ Mill= ion) Figure 76: Philippines Wearable Device Shipments: 2018 =96 2030 (Millions o= f Units) Figure 77: Philippines Wearable Device Shipment Revenue: 2018 =96 2030 ($ M= illion) Figure 78: Singapore Wearable Device Shipments: 2018 =96 2030 (Millions of = Units) Figure 79: Singapore Wearable Device Shipment Revenue: 2018 =96 2030 ($ Mil= lion) Figure 80: South Korea Wearable Device Shipments: 2018 =96 2030 (Millions o= f Units) Figure 81: South Korea Wearable Device Shipment Revenue: 2018 =96 2030 ($ M= illion) Figure 82: Taiwan Wearable Device Shipments: 2018 =96 2030 (Millions of Uni= ts) Figure 83: Taiwan Wearable Device Shipment Revenue: 2018 =96 2030 ($ Millio= n) Figure 84: Thailand Wearable Device Shipments: 2018 =96 2030 (Millions of U= nits) Figure 85: Thailand Wearable Device Shipment Revenue: 2018 =96 2030 ($ Mill= ion) Figure 86: Vietnam Wearable Device Shipments: 2018 =96 2030 (Millions of Un= its) Figure 87: Vietnam Wearable Device Shipment Revenue: 2018 =96 2030 ($ Milli= on) Figure 88: Rest of Asia Pacific Wearable Device Shipments: 2018 =96 2030 (M= illions of Units) Figure 89: Rest of Asia Pacific Wearable Device Shipment Revenue: 2018 =96 = 2030 ($ Million) Figure 90: North America Wearable Device Shipments: 2018 =96 2030 (Millions= of Units) Figure 91: North America Wearable Device Shipment Revenue: 2018 =96 2030 ($= Million) Figure 92: Canada Wearable Device Shipments: 2018 =96 2030 (Millions of Uni= ts) Figure 93: Canada Wearable Device Shipment Revenue: 2018 =96 2030 ($ Millio= n) Figure 94: USA Wearable Device Shipments: 2018 =96 2030 (Millions of Units) Figure 95: USA Wearable Device Shipment Revenue: 2018 =96 2030 ($ Million) Figure 96: Western Europe Wearable Device Shipments: 2018 =96 2030 (Million= s of Units) Figure 97: Western Europe Wearable Device Shipment Revenue: 2018 =96 2030 (= $ Million) Figure 98: Austria Wearable Device Shipments: 2018 =96 2030 (Millions of Un= its) Figure 99: Austria Wearable Device Shipment Revenue: 2018 =96 2030 ($ Milli= on) Figure 100: Belgium Wearable Device Shipments: 2018 =96 2030 (Millions of U= nits) Figure 101: Belgium Wearable Device Shipment Revenue: 2018 =96 2030 ($ Mill= ion) Figure 102: Denmark Wearable Device Shipments: 2018 =96 2030 (Millions of U= nits) Figure 103: Denmark Wearable Device Shipment Revenue: 2018 =96 2030 ($ Mill= ion) Figure 104: Finland Wearable Device Shipments: 2018 =96 2030 (Millions of U= nits) Figure 105: Finland Wearable Device Shipment Revenue: 2018 =96 2030 ($ Mill= ion) Figure 106: France Wearable Device Shipments: 2018 =96 2030 (Millions of Un= its) Figure 107: France Wearable Device Shipment Revenue: 2018 =96 2030 ($ Milli= on) Figure 108: Germany Wearable Device Shipments: 2018 =96 2030 (Millions of U= nits) Figure 109: Germany Wearable Device Shipment Revenue: 2018 =96 2030 ($ Mill= ion) Figure 110: Greece Wearable Device Shipments: 2018 =96 2030 (Millions of Un= its) Figure 111: Greece Wearable Device Shipment Revenue: 2018 =96 2030 ($ Milli= on) Figure 112: Ireland Wearable Device Shipments: 2018 =96 2030 (Millions of U= nits) Figure 113: Ireland Wearable Device Shipment Revenue: 2018 =96 2030 ($ Mill= ion) Figure 114: Italy Wearable Device Shipments: 2018 =96 2030 (Millions of Uni= ts) Figure 115: Italy Wearable Device Shipment Revenue: 2018 =96 2030 ($ Millio= n) Figure 116: Luxembourg Wearable Device Shipments: 2018 =96 2030 (Millions o= f Units) Figure 117: Luxembourg Wearable Device Shipment Revenue: 2018 =96 2030 ($ M= illion) Figure 118: Netherlands Wearable Device Shipments: 2018 =96 2030 (Millions = of Units) Figure 119: Netherlands Wearable Device Shipment Revenue: 2018 =96 2030 ($ = Million) Figure 120: Norway Wearable Device Shipments: 2018 =96 2030 (Millions of Un= its) Figure 121: Norway Wearable Device Shipment Revenue: 2018 =96 2030 ($ Milli= on) Figure 122: Portugal Wearable Device Shipments: 2018 =96 2030 (Millions of = Units) Figure 123: Portugal Wearable Device Shipment Revenue: 2018 =96 2030 ($ Mil= lion) Figure 124: Spain Wearable Device Shipments: 2018 =96 2030 (Millions of Uni= ts) Figure 125: Spain Wearable Device Shipment Revenue: 2018 =96 2030 ($ Millio= n) Figure 126: Sweden Wearable Device Shipments: 2018 =96 2030 (Millions of Un= its) Figure 127: Sweden Wearable Device Shipment Revenue: 2018 =96 2030 ($ Milli= on) Figure 128: Switzerland Wearable Device Shipments: 2018 =96 2030 (Millions = of Units) Figure 129: Switzerland Wearable Device Shipment Revenue: 2018 =96 2030 ($ = Million) Figure 130: Turkey Wearable Device Shipments: 2018 =96 2030 (Millions of Un= its) Figure 131: Turkey Wearable Device Shipment Revenue: 2018 =96 2030 ($ Milli= on) Figure 132: UK Wearable Device Shipments: 2018 =96 2030 (Millions of Units) Figure 133: UK Wearable Device Shipment Revenue: 2018 =96 2030 ($ Million) Figure 134: Rest of Western Europe Wearable Device Shipments: 2018 =96 2030= (Millions of Units) Figure 135: Rest of Western Europe Wearable Device Shipment Revenue: 2018 = =96 2030 ($ Million) Figure 136: Eastern Europe Wearable Device Shipments: 2018 =96 2030 (Millio= ns of Units) Figure 137: Eastern Europe Wearable Device Shipment Revenue: 2018 =96 2030 = ($ Million) Figure 138: Belarus Wearable Device Shipments: 2018 =96 2030 (Millions of U= nits) Figure 139: Belarus Wearable Device Shipment Revenue: 2018 =96 2030 ($ Mill= ion) Figure 140: Bosnia & Herzegovina Wearable Device Shipments: 2018 =96 2030 (= Millions of Units) Figure 141: Bosnia & Herzegovina Wearable Device Shipment Revenue: 2018 =96= 2030 ($ Million) Figure 142: Bulgaria Wearable Device Shipments: 2018 =96 2030 (Millions of = Units) Figure 143: Bulgaria Wearable Device Shipment Revenue: 2018 =96 2030 ($ Mil= lion) Figure 144: Croatia Wearable Device Shipments: 2018 =96 2030 (Millions of U= nits) Figure 145: Croatia Wearable Device Shipment Revenue: 2018 =96 2030 ($ Mill= ion) Figure 146: Czech Republic Wearable Device Shipments: 2018 =96 2030 (Millio= ns of Units) Figure 147: Czech Republic Wearable Device Shipment Revenue: 2018 =96 2030 = ($ Million) Figure 148: Hungary Wearable Device Shipments: 2018 =96 2030 (Millions of U= nits) Figure 149: Hungary Wearable Device Shipment Revenue: 2018 =96 2030 ($ Mill= ion) Figure 150: Poland Wearable Device Shipments: 2018 =96 2030 (Millions of Un= its) Figure 151: Poland Wearable Device Shipment Revenue: 2018 =96 2030 ($ Milli= on) Figure 152: Romania Wearable Device Shipments: 2018 =96 2030 (Millions of U= nits) Figure 153: Romania Wearable Device Shipment Revenue: 2018 =96 2030 ($ Mill= ion) Figure 154: Russia Wearable Device Shipments: 2018 =96 2030 (Millions of Un= its) Figure 155: Russia Wearable Device Shipment Revenue: 2018 =96 2030 ($ Milli= on) Figure 156: Serbia Wearable Device Shipments: 2018 =96 2030 (Millions of Un= its) Figure 157: Serbia Wearable Device Shipment Revenue: 2018 =96 2030 ($ Milli= on) Figure 158: Slovakia Wearable Device Shipments: 2018 =96 2030 (Millions of = Units) Figure 159: Slovakia Wearable Device Shipment Revenue: 2018 =96 2030 ($ Mil= lion) Figure 160: Ukraine Wearable Device Shipments: 2018 =96 2030 (Millions of U= nits) Figure 161: Ukraine Wearable Device Shipment Revenue: 2018 =96 2030 ($ Mill= ion) Figure 162: Uzbekistan Wearable Device Shipments: 2018 =96 2030 (Millions o= f Units) Figure 163: Uzbekistan Wearable Device Shipment Revenue: 2018 =96 2030 ($ M= illion) Figure 164: Rest of Eastern Europe Wearable Device Shipments: 2018 =96 2030= (Millions of Units) Figure 165: Rest of Eastern Europe Wearable Device Shipment Revenue: 2018 = =96 2030 ($ Million) Figure 166: Middle East & Africa Wearable Device Shipments: 2018 =96 2030 (= Millions of Units) Figure 167: Middle East & Africa Wearable Device Shipment Revenue: 2018 =96= 2030 ($ Million) Figure 168: Algeria Wearable Device Shipments: 2018 =96 2030 (Millions of U= nits) Figure 169: Algeria Wearable Device Shipment Revenue: 2018 =96 2030 ($ Mill= ion) Figure 170: Egypt Wearable Device Shipments: 2018 =96 2030 (Millions of Uni= ts) Figure 171: Egypt Wearable Device Shipment Revenue: 2018 =96 2030 ($ Millio= n) Figure 172: Israel Wearable Device Shipments: 2018 =96 2030 (Millions of Un= its) Figure 173: Israel Wearable Device Shipment Revenue: 2018 =96 2030 ($ Milli= on) Figure 174: Kenya Wearable Device Shipments: 2018 =96 2030 (Millions of Uni= ts) Figure 175: Kenya Wearable Device Shipment Revenue: 2018 =96 2030 ($ Millio= n) Figure 176: Morocco Wearable Device Shipments: 2018 =96 2030 (Millions of U= nits) Figure 177: Morocco Wearable Device Shipment Revenue: 2018 =96 2030 ($ Mill= ion) Figure 178: Nigeria Wearable Device Shipments: 2018 =96 2030 (Millions of U= nits) Figure 179: Nigeria Wearable Device Shipment Revenue: 2018 =96 2030 ($ Mill= ion) Figure 180: Qatar Wearable Device Shipments: 2018 =96 2030 (Millions of Uni= ts) Figure 181: Qatar Wearable Device Shipment Revenue: 2018 =96 2030 ($ Millio= n) Figure 182: Saudi Arabia Wearable Device Shipments: 2018 =96 2030 (Millions= of Units) Figure 183: Saudi Arabia Wearable Device Shipment Revenue: 2018 =96 2030 ($= Million) Figure 184: South Africa Wearable Device Shipments: 2018 =96 2030 (Millions= of Units) Figure 185: South Africa Wearable Device Shipment Revenue: 2018 =96 2030 ($= Million) Figure 186: Sudan Wearable Device Shipments: 2018 =96 2030 (Millions of Uni= ts) Figure 187: Sudan Wearable Device Shipment Revenue: 2018 =96 2030 ($ Millio= n) Figure 188: Tanzania Wearable Device Shipments: 2018 =96 2030 (Millions of = Units) Figure 189: Tanzania Wearable Device Shipment Revenue: 2018 =96 2030 ($ Mil= lion) Figure 190: Tunisia Wearable Device Shipments: 2018 =96 2030 (Millions of U= nits) Figure 191: Tunisia Wearable Device Shipment Revenue: 2018 =96 2030 ($ Mill= ion) Figure 192: UAE Wearable Device Shipments: 2018 =96 2030 (Millions of Units) Figure 193: UAE Wearable Device Shipment Revenue: 2018 =96 2030 ($ Million) Figure 194: Rest of the Middle East & Africa Wearable Device Shipments: 201= 8 =96 2030 (Millions of Units) Figure 195: Rest of the Middle East & Africa Wearable Device Shipment Reven= ue: 2018 =96 2030 ($ Million) Figure 196: Latin & Central America Wearable Device Shipments: 2018 =96 203= 0 (Millions of Units) Figure 197: Latin & Central America Wearable Device Shipment Revenue: 2018 = =96 2030 ($ Million) Figure 198: Argentina Wearable Device Shipments: 2018 =96 2030 (Millions of= Units) Figure 199: Argentina Wearable Device Shipment Revenue: 2018 =96 2030 ($ Mi= llion) Figure 200: Bolivia Wearable Device Shipments: 2018 =96 2030 (Millions of U= nits) Figure 201: Bolivia Wearable Device Shipment Revenue: 2018 =96 2030 ($ Mill= ion) Figure 202: Brazil Wearable Device Shipments: 2018 =96 2030 (Millions of Un= its) Figure 203: Brazil Wearable Device Shipment Revenue: 2018 =96 2030 ($ Milli= on) Figure 204: Chile Wearable Device Shipments: 2018 =96 2030 (Millions of Uni= ts) Figure 205: Chile Wearable Device Shipment Revenue: 2018 =96 2030 ($ Millio= n) Figure 206: Colombia Wearable Device Shipments: 2018 =96 2030 (Millions of = Units) Figure 207: Colombia Wearable Device Shipment Revenue: 2018 =96 2030 ($ Mil= lion) Figure 208: Ecuador Wearable Device Shipments: 2018 =96 2030 (Millions of U= nits) Figure 209: Ecuador Wearable Device Shipment Revenue: 2018 =96 2030 ($ Mill= ion) Figure 210: Mexico Wearable Device Shipments: 2018 =96 2030 (Millions of Un= its) Figure 211: Mexico Wearable Device Shipment Revenue: 2018 =96 2030 ($ Milli= on) Figure 212: Paraguay Wearable Device Shipments: 2018 =96 2030 (Millions of = Units) Figure 213: Paraguay Wearable Device Shipment Revenue: 2018 =96 2030 ($ Mil= lion) Figure 214: Peru Wearable Device Shipments: 2018 =96 2030 (Millions of Unit= s) Figure 215: Peru Wearable Device Shipment Revenue: 2018 =96 2030 ($ Million) Figure 216: Uruguay Wearable Device Shipments: 2018 =96 2030 (Millions of U= nits) Figure 217: Uruguay Wearable Device Shipment Revenue: 2018 =96 2030 ($ Mill= ion) Figure 218: Venezuela Wearable Device Shipments: 2018 =96 2030 (Millions of= Units) Figure 219: Venezuela Wearable Device Shipment Revenue: 2018 =96 2030 ($ Mi= llion) Figure 220: Rest of Latin & Central America Wearable Device Shipments: 2018= =96 2030 (Millions of Units) Figure 221: Rest of Latin & Central America Wearable Device Shipment Revenu= e: 2018 =96 2030 ($ Million) Figure 222: Global Wearable Device Unit Shipment Breakdown by Form Factor: = 2021 (%) Figure 223: Global Wearable Device Shipment Market Share by Vendor: 2017 (%) Figure 224: Global Cellular Chipset Shipments for Wearable Devices: 2018 = =96 2030 (Millions of Units) Figure 225: Global Wearable Driven Mobile Operator Service Revenue by Form = Factor: 2018 =96 2030 ($ Million) Figure 226: Fashion Centric Wearables Figure 227: Global Wearable Applications Ecosystem Revenue by Vertical: 201= 8 =96 2030 ($ Million) Figure 228: Global Wrist-Worn Wearable Device Shipments by Key Application = Areas: 2018 =96 2030 (Millions of Units) Figure 229: Global Fitness & Sports Centric Wearable Device Shipments by Ca= tegory: 2018 =96 2030 (Millions of Units) Figure 230: Global Fitness & Sports Centric Wearable Device Shipment Revenu= e by Category: 2018 =96 2030 ($ Million) Thank you once again and looking forward to hearing from you. =20 Kind Regards =20 Andy Silva Marketing Executive Signals and Systems Telecom =20 =20 To unsubscribe send an email with unsubscribe in the subject line to: remov= e@snsreports.com =20 From owner-freebsd-ppc@freebsd.org Mon May 7 22:13:07 2018 Return-Path: Delivered-To: freebsd-ppc@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 995A2FBE6E6 for ; Mon, 7 May 2018 22:13:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 36D3D7DC98 for ; Mon, 7 May 2018 22:13:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by freefall.freebsd.org (Postfix) id 28C5DAA84; Mon, 7 May 2018 22:13:07 +0000 (UTC) Delivered-To: powerpc@localmail.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by freefall.freebsd.org (Postfix) with ESMTPS id 260BAAA83 for ; Mon, 7 May 2018 22:13:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E93C77DC88 for ; Mon, 7 May 2018 22:13:06 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 2761A1D16D for ; Mon, 7 May 2018 22:13:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w47MD6Th068395 for ; Mon, 7 May 2018 22:13:06 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w47MD6sp068393 for powerpc@FreeBSD.org; Mon, 7 May 2018 22:13:06 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: powerpc@FreeBSD.org Subject: [Bug 228055] lang/gcl fails to compile on powerpc64 Date: Mon, 07 May 2018 22:13:06 +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: hamiltcl@verizon.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ports-bugs@FreeBSD.org X-Bugzilla-Flags: 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.25 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 May 2018 22:13:07 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D228055 --- Comment #1 from Curtis Hamilton --- To get past the initial error, I added the below lines to 'elf64_ppc_reloc.h +case R_PPC64_REL24: + store_ival((int *)where,~0L,(s+a-p)); + break; OPTIMIZE levels: Safety=3D1 (No runtime error checking), Space=3D0, Speed= =3D3 Finished compiling /usr/ports/lang/gcl/work/gcl/unixport/../pcl/gcl_pcl_fin= .o. Loading binary of GCL_PCL_FIN... Loading /usr/ports/lang/gcl/work/gcl/unixport/../pcl/gcl_pcl_fin.o start address -T 0x113609c0 Finished loading /usr/ports/lang/gcl/work/gcl/unixport/../pcl/gcl_pcl_fin.o Compiling GCL_PCL_DEFCLASS... Compiling /usr/ports/lang/gcl/work/gcl/unixport/../pcl/gcl_pcl_defclass.lis= p. Error: UNDEFINED-FUNCTION :NAME ITERATE::OPTIMIZE-GATHERING-FORM Fast links are on: do (si::use-fast-links nil) for debugging Signalled by LET. UNDEFINED-FUNCTION :NAME ITERATE::OPTIMIZE-GATHERING-FORM Broken at LET. Type :H for Help. 1 Return to top level. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-ppc@freebsd.org Tue May 8 01:27:58 2018 Return-Path: Delivered-To: freebsd-ppc@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 6F0E9FC5386 for ; Tue, 8 May 2018 01:27:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 019B96D2D7 for ; Tue, 8 May 2018 01:27:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id AFFD6FC5382; Tue, 8 May 2018 01:27:57 +0000 (UTC) Delivered-To: ppc@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 9C010FC5381 for ; Tue, 8 May 2018 01:27:57 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 339C96D2D5 for ; Tue, 8 May 2018 01:27:57 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 5E9B51EC1C for ; Tue, 8 May 2018 01:27:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w481Ru5U044968 for ; Tue, 8 May 2018 01:27:56 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w481Rufg044967 for ppc@FreeBSD.org; Tue, 8 May 2018 01:27:56 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: ppc@FreeBSD.org Subject: [Bug 228056] powerpc64: MCE on POWER9 machine (AC922) Date: Tue, 08 May 2018 01:27:56 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ppc@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to 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.25 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 May 2018 01:27:58 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D228056 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bugs@FreeBSD.org |ppc@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-ppc@freebsd.org Wed May 9 21:40:18 2018 Return-Path: Delivered-To: freebsd-ppc@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 3F0E7FCD538 for ; Wed, 9 May 2018 21:40:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 85D5277E7D for ; Wed, 9 May 2018 21:40:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id AB12FFCD527; Wed, 9 May 2018 21:40:16 +0000 (UTC) Delivered-To: ppc@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 8621DFCD525 for ; Wed, 9 May 2018 21:40:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BF4C377E17 for ; Wed, 9 May 2018 21:40:14 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id E7C64161A4 for ; Wed, 9 May 2018 21:40:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w49LeDL5039008 for ; Wed, 9 May 2018 21:40:13 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w49LeDWV039007 for ppc@FreeBSD.org; Wed, 9 May 2018 21:40:13 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: ppc@FreeBSD.org Subject: [Bug 227093] powerpc64/pseries: Symbol table not relocated Date: Wed, 09 May 2018 21:40:13 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: breno.leitao@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: breno.leitao@gmail.com X-Bugzilla-Flags: 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.25 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 May 2018 21:40:18 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D227093 --- Comment #3 from Breno Leitao --- A new revision was made to get this fixed: https://reviews.freebsd.org/D15372 --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-ppc@freebsd.org Thu May 10 04:00:53 2018 Return-Path: Delivered-To: freebsd-ppc@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 29711FADF38 for ; Thu, 10 May 2018 04:00:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id B5D80878D2 for ; Thu, 10 May 2018 04:00:52 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 76828FADF2F; Thu, 10 May 2018 04:00:52 +0000 (UTC) Delivered-To: ppc@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 651CEFADF2D for ; Thu, 10 May 2018 04:00:52 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0112B878CD for ; Thu, 10 May 2018 04:00: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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 1ABE119777 for ; Thu, 10 May 2018 04:00:51 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w4A40o6Q000882 for ; Thu, 10 May 2018 04:00:50 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w4A40oxV000878 for ppc@FreeBSD.org; Thu, 10 May 2018 04:00:50 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: ppc@FreeBSD.org Subject: [Bug 227093] powerpc64/pseries: Symbol table not relocated Date: Thu, 10 May 2018 04:00:51 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: breno.leitao@gmail.com X-Bugzilla-Flags: 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.25 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 May 2018 04:00:53 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D227093 --- Comment #4 from commit-hook@freebsd.org --- A commit references this bug: Author: jhibbits Date: Thu May 10 03:59:49 UTC 2018 New revision: 333447 URL: https://svnweb.freebsd.org/changeset/base/333447 Log: Fix PPC symbol resolution Summary: There were 2 issues that were preventing correct symbol resolution on PowerPC/pseries: 1- memory corruption at chrp_attach() - this caused the inital part of the symbol table to become zeroed, which would cause the kernel linker to fail to parse it. (this was probably zeroing out other memory parts as well) 2- DDB symbol resolution wasn't working because symtab contained not relocated addresses but it was given relocated offsets. Although relocating the symbol table fixed this, it broke the linker, that already handled this case. Thus, the fix for this consists in adding a new DDB macro: DB_STOFFS(offs) that converts a (potentially) relocated offset into one that can be compared with symbol table values. PR: 227093 Submitted by: Leandro Lupori Differential Revision: https://reviews.freebsd.org/D15372 Changes: head/sys/ddb/db_main.c head/sys/ddb/ddb.h head/sys/powerpc/include/db_machdep.h head/sys/powerpc/pseries/platform_chrp.c --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-ppc@freebsd.org Fri May 11 02:18:52 2018 Return-Path: Delivered-To: freebsd-ppc@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 E3636FB066B for ; Fri, 11 May 2018 02:18:51 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 7950469FA0 for ; Fri, 11 May 2018 02:18:51 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 3325EFB066A; Fri, 11 May 2018 02:18:51 +0000 (UTC) Delivered-To: ppc@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 1F4FEFB0669 for ; Fri, 11 May 2018 02:18:51 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AC13069F9B for ; Fri, 11 May 2018 02:18: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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id CD10225173 for ; Fri, 11 May 2018 02:18:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w4B2InwQ024216 for ; Fri, 11 May 2018 02:18:49 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w4B2IniB024214 for ppc@FreeBSD.org; Fri, 11 May 2018 02:18:49 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: ppc@FreeBSD.org Subject: [Bug 227093] powerpc64/pseries: Symbol table not relocated Date: Fri, 11 May 2018 02:18:49 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: jhibbits@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: jhibbits@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status assigned_to resolution 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.25 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 May 2018 02:18:52 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D227093 Justin Hibbits changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Closed Assignee|breno.leitao@gmail.com |jhibbits@FreeBSD.org Resolution|--- |FIXED --- Comment #5 from Justin Hibbits --- Fixed in r333447 --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-ppc@freebsd.org Fri May 11 23:09:07 2018 Return-Path: Delivered-To: freebsd-ppc@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 F0282FD323E for ; Fri, 11 May 2018 23:09:06 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic315-9.consmr.mail.gq1.yahoo.com (sonic315-9.consmr.mail.gq1.yahoo.com [98.137.65.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6DB616F967 for ; Fri, 11 May 2018 23:09:06 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: HvDZAWUVM1lA1dNaqvl9B6FP6imVf7BbvnPNSVjN0R3dgcE7p.xFCyevFmZ2OBN 2LcSL2tyrtEjHzQJWa2Ztwv5Zkh9YO790pnAumnu0cfidguR26ToBNz50o8ObdmEYid5Q.FN7Qv4 0va3guASa7PZe3bgjpbKNBs8Eyqh..LzoThxapXqhYof0rhHjiVAzKzEPFBQ4Zd_BAK_9zNIMdUL Zdz_BiXCpxDqc_aa_ikMzvkBCn8mtMp7wpNaeesi4Q1B4Zjc8Pmc5WVJJwtoCShkKzKtiysM6KNp o7RFVk526eDgEs1Hyg751o2PSup83yJMD3gRonQCU9uglb7KQBiYni_0TWxfwyaMb6GWuXGoMuxj TO_yq8yUXvdUYsx9a7ZpTM.7ORI0C6YOFL8RddbH1PeeqnMkc6l2SiBNCcvFOwWtLNn3PQlcL_ON r827kVpAelItPoEyg6t2Ow123PQSFV_49zFncksqMsZuhJYVsU1s5RrDBeuXZAIWTBBrcoId6XQL V_kv8AfITIzRhH9LsXa_U9CEayzwMOMYZV.GykqGV11tCfnY0Jb5szO5Hs_GrgTthOxbNEFn.tpY 9BWy8VbYqqw3y9MSCQ0tFLlLTkeIDaBGYib6.wKPtJSHE8j1gJaijtw-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic315.consmr.mail.gq1.yahoo.com with HTTP; Fri, 11 May 2018 23:09:04 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.25]) ([76.115.7.162]) by smtp413.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID f09537e577fa0b16a6028f42d93762a9; Fri, 11 May 2018 23:09:03 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Subject: What fails when devel/xtoolchain-llvm60 attempts to build powerpc64's lib32 in buildworld cross builds (from amd64 here) Date: Fri, 11 May 2018 16:09:02 -0700 References: <81EA8FB2-101B-4D31-A2D4-91CCB78AF695@yahoo.com> To: freebsd-toolchain@freebsd.org, FreeBSD PowerPC ML In-Reply-To: <81EA8FB2-101B-4D31-A2D4-91CCB78AF695@yahoo.com> Message-Id: X-Mailer: Apple Mail (2.3445.6.18) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 May 2018 23:09:07 -0000 [I experiment with targeting powerpc family members with modern tool chains. In this case trying to use devel/xtoolchain-llvm60 . This was indirectly reached via commenting on a bugzilla entry for something else powerpc family related.] BEGIN setup notes: Because of (at least) lld problems for targeting powerpc family members, the following is based on an alternate toolchains/*.mk : # diff /usr/local/share/toolchains/llvm60.mk = /usr/local/share/toolchains/llvm60_altbinutils.mk 4,5c4,5 < XLD=3D/usr/local/llvm60/bin/ld.lld < CROSS_BINUTILS_PREFIX=3D/var/empty --- =20 > #XLD=3D/usr/local/llvm60/bin/ld.lld > #CROSS_BINUTILS_PREFIX=3D/var/empty This is to allow setting up the use of: CROSS_BINUTILS_PREFIX=3D/usr/local/powerpc64-unknown-freebsd12.0/bin/ END Setup notes. The below is from adding a -v to what the .meta file showed for the = failing command. Note the "-cc1as -triple i386-portbld-freebsd12.0" and "-target-cpu = i486" that results from buildworld=E2=80=99s lib32 related command that tries to compile = assembly source for powerpc. # /usr/local/bin/clang60 -v -DCOMPAT_32BIT -mcpu=3Dpowerpc -m32 = -L/usr/obj/powerpc64vtsc_xtoolchain-llvm/powerpc.powerpc64/usr/src/powerpc= .powerpc64/obj-lib32/tmp/usr/lib32 = tosysroot=3D/usr/obj/powerpc64vtsc_xtoolchain-llvm/powerpc.powerpc64/usr/s= rc/powerpc.powerpc64/obj-lib32/tmp = -B/usr/local/powerpc64-unknown-freebsd12.0/bin = -B/usr/obj/powerpc64vtsc_x -Wall -Wno-format-y2k -W = -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes = -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch = -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline = -Wnested-externs -Wredundant-decls -Wold-style-definition = -Wno-pointer-sign -Wthread-safety -Wno-empty-body -Wno-string-plus-int = -Wno-unused-const-variable -Qunused-arguments -c = /usr/src/lib/csu/powerpc/crtn.S -o crtn.ole-definition -Wno-pointer-sign = -Wthread-safety -Wno-empty-body -Wno-string-plus-int -Wno-unus clang version 6.0.0 = (tags/RELEASE_600/final)/usr/src/lib/csu/powerpc/crtn.S -o crtn.o Target: i386-portbld-freebsd12.0 Thread model: posix InstalledDir: /usr/local/llvm60/bin "/usr/local/llvm60/bin/clang-6.0" -cc1 -triple i386-portbld-freebsd12.0 = -E -disable-free -main-file-name crtn.S -mrelocation-model static = -mthread-model posix -mdisable-fp-elim -masm-verbose = -mconstructor-aliases -target-cpu i486 -dwarf-column-info = -debug-info-kind=3Dstandalone -dwarf-version=3D2 -debugger-tuning=3Dgdb = -v -coverage-notes-file /usr/src/crtn.gcno -resource-dir = /usr/local/llvm60/lib/clang/6.0.0 -D COMPAT_32BIT -I = /usr/src/lib/csu/common -I /usr/src/lib/libc/include -isysroot = /usr/obj/powerpc64vtsc_xtoolchain-llvm/powerpc.powerpc64/usr/src/powerpc.p= owerpc64/obj-lib32/tmp -O2 -Wsystem-headers -Wall -Wno-format-y2k -W = -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes = -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch = -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline = -Wnested-externs -Wredundant-decls -Wold-style-definition = -Wno-pointer-sign -Wthread-safety -Wno-empty-body -Wno-string-plus-int = -Wno-unused-const-variable -std=3Dgnu99 -fconst-strings = -fdebug-compilation-dir /usr/src -ferror-limit 19 -fmessage-length 180 = -fobjc-runtime=3Dgnustep -fdiagnostics-show-option -vectorize-loops = -vectorize-slp -o /tmp/crtn-d80df9.s -x assembler-with-cpp = /usr/src/lib/csu/powerpc/crtn.S clang -cc1 version 6.0.0 based upon LLVM 6.0.0 default target = x86_64-portbld-freebsd12.0 #include "..." search starts here: #include <...> search starts here: /usr/src/lib/csu/common /usr/src/lib/libc/include /usr/local/llvm60/lib/clang/6.0.0/include = /usr/obj/powerpc64vtsc_xtoolchain-llvm/powerpc.powerpc64/usr/src/powerpc.p= owerpc64/obj-lib32/tmp/usr/include End of search list. "/usr/local/llvm60/bin/clang-6.0" -cc1as -triple = i386-portbld-freebsd12.0 -filetype obj -main-file-name crtn.S = -target-cpu i486 -I /usr/src/lib/csu/common -I /usr/src/lib/libc/include = -fdebug-compilation-dir /usr/src -dwarf-debug-producer clang version = 6.0.0 (tags/RELEASE_600/final) -I /usr/src/lib/csu/common -I = /usr/src/lib/libc/include -debug-info-kind=3Dlimited -dwarf-version=3D2 = -mrelocation-model static -o crtn.o /tmp/crtn-d80df9.s /usr/src/lib/csu/powerpc/crtn.S:29:2: warning: DWARF2 only supports one = section per compilation unit .section .init,"ax",@progbits ^ /usr/src/lib/csu/powerpc/crtn.S:30:11: error: unexpected token in memory = operand lwz 11,0(1) ^ /usr/src/lib/csu/powerpc/crtn.S:31:10: error: unexpected token in memory = operand lwz 0,4(11) ^ /usr/src/lib/csu/powerpc/crtn.S:32:2: error: invalid instruction = mnemonic 'mtlr' mtlr 0 ^~~~ . . . It would appear that a -triple may be missing in the = /usr/local/bin/clang60 command line that would specify the specific ABI to target. It appears = that the -mcpu=3Dpowerpc is not enough to even get the cpu family right as = far as what assembler notation to process. I do not know if an appropriate -triple addition would currently be sufficient for things to start working. Something needs to cause the right assembler notation to be processed = for lib32 if WITH_LIB32=3D is to be supported for cross builds. =3D=3D=3D Mark Millard marklmi26-fbsd at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-ppc@freebsd.org Sat May 12 05:28:02 2018 Return-Path: Delivered-To: freebsd-ppc@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 26147FB4289 for ; Sat, 12 May 2018 05:28:02 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic316-15.consmr.mail.bf2.yahoo.com (sonic316-15.consmr.mail.bf2.yahoo.com [74.6.130.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BFD78814D7 for ; Sat, 12 May 2018 05:28:01 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: YUy8nkMVM1m1R313S3RcVA6fHykTX04F8rw6WAEUShREA4hgxxdcroci_m6WJEa ahMpGZcKGEQdl2YMwDyalY0Y65jFXhrNdJbbD3RYE24RQ7fHPyu5KRz.tr8gKSrkzKtB3BbG_Gb2 vuZM_Giw5fcl3dstl2qp5yFv.b4BX9ynHbBCD5BEgHG9Gjm1JEBP0VrxccjQ41dOkw6kMyPbsHra NIl.FJLqb7ik_K0RYpSlDhvf5.btncdJQIT4w_WtICflboEvkm6XoUYmcFOIZBQC0djbc0CQOcz5 tp45ivFiF8oYuz3qGtwXjpU_ko12UkP9rGGMfp75afJOC2Mr7C6BF86pPdSl6INA5IqC8MNfLZ5q 63nEmnm8deBjmYRPVEvdkTRVG_jz3HkY4owoBeyhuZpwZ.wzy4rG6v2JQKF5RSF2tiqMTZ0blwqh AUF00AUMT1UXrUy.72zsbAAM.MxHrHwrxUti.cGCBa029KXcVMPfAciroVkPEU35PCWEQwyEMqZg z95Ts4MlxuNDMEd0j18.wApOoTV9z8HaRek3gjXDhCRIeB.1B.VmneIb2jmP1p9ztg8PwCdCHCuG ielcBagM0ywO535vBlVOdxHRC8BTx1Xv_Pk6ePCFaMTfnu.epqy2vhOxJVHc2joNIZACo9Jvsv18 I5IY- Received: from sonic.gate.mail.ne1.yahoo.com by sonic316.consmr.mail.bf2.yahoo.com with HTTP; Sat, 12 May 2018 05:27:55 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.25]) ([76.115.7.162]) by smtp401.mail.bf1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 5d145dba65231755fbe645c632627545; Sat, 12 May 2018 05:07:40 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Subject: Re: What fails when devel/xtoolchain-llvm60 attempts to build powerpc64's lib32 in buildworld cross builds (from amd64 here) Date: Fri, 11 May 2018 22:07:38 -0700 References: <81EA8FB2-101B-4D31-A2D4-91CCB78AF695@yahoo.com> To: freebsd-toolchain@freebsd.org, FreeBSD PowerPC ML In-Reply-To: Message-Id: <0AAA00A2-5C78-44FF-AFFE-5D796A22EBC7@yahoo.com> X-Mailer: Apple Mail (2.3445.6.18) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 May 2018 05:28:02 -0000 On 2018-May-11, at 4:09 PM, Mark Millard = wrote: > [I experiment with targeting powerpc family members with > modern tool chains. In this case trying to use > devel/xtoolchain-llvm60 . This was indirectly reached via > commenting on a bugzilla entry for something else powerpc > family related.] >=20 > BEGIN setup notes: >=20 > Because of (at least) lld problems for targeting powerpc family = members, > the following is based on an alternate toolchains/*.mk : >=20 > # diff /usr/local/share/toolchains/llvm60.mk = /usr/local/share/toolchains/llvm60_altbinutils.mk > 4,5c4,5 > < XLD=3D/usr/local/llvm60/bin/ld.lld > < CROSS_BINUTILS_PREFIX=3D/var/empty > --- >=20 >> #XLD=3D/usr/local/llvm60/bin/ld.lld >> #CROSS_BINUTILS_PREFIX=3D/var/empty >=20 > This is to allow setting up the use of: >=20 > CROSS_BINUTILS_PREFIX=3D/usr/local/powerpc64-unknown-freebsd12.0/bin/ >=20 > END Setup notes. >=20 > The below is from adding a -v to what the .meta file showed for the = failing command. > Note the "-cc1as -triple i386-portbld-freebsd12.0" and "-target-cpu = i486" that results > from buildworld=E2=80=99s lib32 related command that tries to compile = assembly source for > powerpc. >=20 >=20 > # /usr/local/bin/clang60 -v -DCOMPAT_32BIT -mcpu=3Dpowerpc -m32 = -L/usr/obj/powerpc64vtsc_xtoolchain-llvm/powerpc.powerpc64/usr/src/powerpc= .powerpc64/obj-lib32/tmp/usr/lib32 = tosysroot=3D/usr/obj/powerpc64vtsc_xtoolchain-llvm/powerpc.powerpc64/usr/s= rc/powerpc.powerpc64/obj-lib32/tmp = -B/usr/local/powerpc64-unknown-freebsd12.0/bin = -B/usr/obj/powerpc64vtsc_x -Wall -Wno-format-y2k -W = -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes = -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch = -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline = -Wnested-externs -Wredundant-decls -Wold-style-definition = -Wno-pointer-sign -Wthread-safety -Wno-empty-body -Wno-string-plus-int = -Wno-unused-const-variable -Qunused-arguments -c = /usr/src/lib/csu/powerpc/crtn.S -o crtn.ole-definition -Wno-pointer-sign = -Wthread-safety -Wno-empty-body -Wno-string-plus-int -Wno-unus > clang version 6.0.0 = (tags/RELEASE_600/final)/usr/src/lib/csu/powerpc/crtn.S -o crtn.o > Target: i386-portbld-freebsd12.0 > Thread model: posix > InstalledDir: /usr/local/llvm60/bin > "/usr/local/llvm60/bin/clang-6.0" -cc1 -triple = i386-portbld-freebsd12.0 -E -disable-free -main-file-name crtn.S = -mrelocation-model static -mthread-model posix -mdisable-fp-elim = -masm-verbose -mconstructor-aliases -target-cpu i486 -dwarf-column-info = -debug-info-kind=3Dstandalone -dwarf-version=3D2 -debugger-tuning=3Dgdb = -v -coverage-notes-file /usr/src/crtn.gcno -resource-dir = /usr/local/llvm60/lib/clang/6.0.0 -D COMPAT_32BIT -I = /usr/src/lib/csu/common -I /usr/src/lib/libc/include -isysroot = /usr/obj/powerpc64vtsc_xtoolchain-llvm/powerpc.powerpc64/usr/src/powerpc.p= owerpc64/obj-lib32/tmp -O2 -Wsystem-headers -Wall -Wno-format-y2k -W = -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes = -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch = -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline = -Wnested-externs -Wredundant-decls -Wold-style-definition = -Wno-pointer-sign -Wthread-safety -Wno-empty-body -Wno-string-plus-int = -Wno-unused-const-variable -std=3Dgnu99 -fconst-strings = -fdebug-compilation-dir /usr/src -ferror-limit 19 -fmessage-length 180 = -fobjc-runtime=3Dgnustep -fdiagnostics-show-option -vectorize-loops = -vectorize-slp -o /tmp/crtn-d80df9.s -x assembler-with-cpp = /usr/src/lib/csu/powerpc/crtn.S > clang -cc1 version 6.0.0 based upon LLVM 6.0.0 default target = x86_64-portbld-freebsd12.0 > #include "..." search starts here: > #include <...> search starts here: > /usr/src/lib/csu/common > /usr/src/lib/libc/include > /usr/local/llvm60/lib/clang/6.0.0/include > = /usr/obj/powerpc64vtsc_xtoolchain-llvm/powerpc.powerpc64/usr/src/powerpc.p= owerpc64/obj-lib32/tmp/usr/include > End of search list. > "/usr/local/llvm60/bin/clang-6.0" -cc1as -triple = i386-portbld-freebsd12.0 -filetype obj -main-file-name crtn.S = -target-cpu i486 -I /usr/src/lib/csu/common -I /usr/src/lib/libc/include = -fdebug-compilation-dir /usr/src -dwarf-debug-producer clang version = 6.0.0 (tags/RELEASE_600/final) -I /usr/src/lib/csu/common -I = /usr/src/lib/libc/include -debug-info-kind=3Dlimited -dwarf-version=3D2 = -mrelocation-model static -o crtn.o /tmp/crtn-d80df9.s > /usr/src/lib/csu/powerpc/crtn.S:29:2: warning: DWARF2 only supports = one section per compilation unit > .section .init,"ax",@progbits > ^ > /usr/src/lib/csu/powerpc/crtn.S:30:11: error: unexpected token in = memory operand > lwz 11,0(1) > ^ > /usr/src/lib/csu/powerpc/crtn.S:31:10: error: unexpected token in = memory operand > lwz 0,4(11) > ^ > /usr/src/lib/csu/powerpc/crtn.S:32:2: error: invalid instruction = mnemonic 'mtlr' > mtlr 0 > ^~~~ > . . . >=20 >=20 >=20 > It would appear that a -triple may be missing in the = /usr/local/bin/clang60 > command line that would specify the specific ABI to target. It appears = that > the -mcpu=3Dpowerpc is not enough to even get the cpu family right as = far as > what assembler notation to process. >=20 > I do not know if an appropriate -triple addition would currently be > sufficient for things to start working. >=20 > Something needs to cause the right assembler notation to be processed = for > lib32 if WITH_LIB32=3D is to be supported for cross builds. Kenneth Salerno's = https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D227920 is an example patch for 11.1 for this lack of -target use where it can = be needed. =3D=3D=3D Mark Millard marklmi26-fbsd at yahoo.com ( dsl-only.net went away in early 2018-Mar)