From owner-freebsd-ppc@freebsd.org Sun Mar 6 01:13:29 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EF9469DB98E for ; Sun, 6 Mar 2016 01:13:29 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-1.reflexion.net [208.70.210.1]) (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 8BEC17F5 for ; Sun, 6 Mar 2016 01:13:29 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 31153 invoked from network); 6 Mar 2016 01:13:20 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 6 Mar 2016 01:13:20 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v7.80.0) with SMTP; Sat, 05 Mar 2016 20:13:37 -0500 (EST) Received: (qmail 12143 invoked from network); 6 Mar 2016 01:13:37 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with SMTP; 6 Mar 2016 01:13:37 -0000 X-No-Relay: not in my network X-No-Relay: not in my network X-No-Relay: not in my network Received: from [192.168.1.8] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 2656A1C43D7; Sat, 5 Mar 2016 17:13:17 -0800 (PST) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: 207732 submitted: libgcc_s .eh_frame handling messes up interpreting powerpc/powerpc64 frame pointer register use produced by clang 3.8.0 Message-Id: <7BC7F7FF-FF5C-4BE9-875C-6997BC194295@dsl-only.net> Date: Sat, 5 Mar 2016 17:13:21 -0800 To: Roman Divacky , FreeBSD PowerPC ML , FreeBSD Toolchain Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.21 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 Mar 2016 01:13:30 -0000 I have submitted FreeBSD bug 207732: libgcc_s .eh_frame handling messes up interpreting powerpc/powerpc64 = frame pointer register use produced by clang 3.8.0 In essence clang++ 3.8.0 generates Frame Pointer Register based code = (r31 in addition to the r1 stack pointer) that g++ 4.2.1/4.9/5.3 = (normally) do not and so the clang++ 3.8.0 code ends up touching an = error in libgcc_s interpreting .eh_frame information for C++ exception = handling that gcc 4.2.1 and the like side step by not using such a Frame = Pointer register. Note: The context for libgcc_s was a clang 3.8.0 based buildworld. A gcc = buildworld does not involve such a Frame Pointer Register. I do not know if any TARGET_ARCH's other than powerpc/powerpc64 also = generate such Frame Pointer Register like code and so might touch the = same error. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Sun Mar 6 08:19:46 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 028029DA3FA for ; Sun, 6 Mar 2016 08:19:46 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-2.reflexion.net [208.70.210.2]) (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 AB3F3305 for ; Sun, 6 Mar 2016 08:19:45 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 12510 invoked from network); 6 Mar 2016 08:20:02 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 6 Mar 2016 08:20:02 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v7.80.0) with SMTP; Sun, 06 Mar 2016 03:19:47 -0500 (EST) Received: (qmail 5983 invoked from network); 6 Mar 2016 08:19:47 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with SMTP; 6 Mar 2016 08:19:47 -0000 X-No-Relay: not in my network X-No-Relay: not in my network X-No-Relay: not in my network Received: from [192.168.1.8] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 58D181C43D7; Sun, 6 Mar 2016 00:19:43 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: 207732 submitted: libgcc_s .eh_frame handling messes up interpreting powerpc/powerpc64 frame pointer register use produced by clang 3.8.0 [I was wrong] From: Mark Millard In-Reply-To: <7BC7F7FF-FF5C-4BE9-875C-6997BC194295@dsl-only.net> Date: Sun, 6 Mar 2016 00:19:42 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <76083A2C-9659-46A9-B9DC-6944C50AF4E9@dsl-only.net> References: <7BC7F7FF-FF5C-4BE9-875C-6997BC194295@dsl-only.net> To: Roman Divacky , FreeBSD PowerPC ML , FreeBSD Toolchain X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.21 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 Mar 2016 08:19:46 -0000 On 2016-Mar-5, at 5:13 PM, Mark Millard wrote: >=20 > I have submitted FreeBSD bug 207732: >=20 > libgcc_s .eh_frame handling messes up interpreting powerpc/powerpc64 = frame pointer register use produced by clang 3.8.0 >=20 > In essence clang++ 3.8.0 generates Frame Pointer Register based code = (r31 in addition to the r1 stack pointer) that g++ 4.2.1/4.9/5.3 = (normally) do not and so the clang++ 3.8.0 code ends up touching an = error in libgcc_s interpreting .eh_frame information for C++ exception = handling that gcc 4.2.1 and the like side step by not using such a Frame = Pointer register. >=20 > Note: The context for libgcc_s was a clang 3.8.0 based buildworld. A = gcc buildworld does not involve such a Frame Pointer Register. >=20 > I do not know if any TARGET_ARCH's other than powerpc/powerpc64 also = generate such Frame Pointer Register like code and so might touch the = same error. >=20 >=20 > =3D=3D=3D > Mark Millard > markmi at dsl-only.net With the other errors identified and reported for .eh_frame and C++ = exception handling for powerpc it is getting harder to tell if a problem = is a new problem or a consequence of the other ones. (Various problems = have no work around yet to avoid them.) This turned out to be a consequence of other problems. Such was easier to discover once I induced gcc 4.2.1 to generate some = example code with r31 in use as a frame pointer. (I used alloca and = default optimization.) Observing the result's behavior and the .eh_frame = output indicated I'd originally misinterpreted where the earliest = problem was in the clang 3.8.0 context. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Sun Mar 6 11:48:49 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DB625AB724C for ; Sun, 6 Mar 2016 11:48:49 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-1.reflexion.net [208.70.210.1]) (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 90E1A894 for ; Sun, 6 Mar 2016 11:48:48 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 26981 invoked from network); 6 Mar 2016 11:48:45 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 6 Mar 2016 11:48:45 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v7.80.0) with SMTP; Sun, 06 Mar 2016 06:49:02 -0500 (EST) Received: (qmail 1110 invoked from network); 6 Mar 2016 11:49:02 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with SMTP; 6 Mar 2016 11:49:02 -0000 X-No-Relay: not in my network X-No-Relay: not in my network X-No-Relay: not in my network Received: from [192.168.1.8] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id BF3FC1C43CC; Sun, 6 Mar 2016 03:48:45 -0800 (PST) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Bug 207736 submitted for TARGET_ARCH=powerpc (& ppc64?) clang 3.8.0 frame-pointer code generation error for _Unwind_RaiseException Message-Id: Date: Sun, 6 Mar 2016 03:48:46 -0800 To: Roman Divacky , FreeBSD PowerPC ML , FreeBSD Toolchain Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.21 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 Mar 2016 11:48:50 -0000 [This has been reported on llvm bugzilla: 26856.] The below causes gdb difficulties for its stack handling: more than just = exception handling is at issue. I just happened to notice it via = exception handling. Function _Unwind_RaiseException below is from a FreeBSD = TARGET_ARCH=3Dpowerpc "buildworld" using clang 3.8.0. Dump of assembler code for function _Unwind_RaiseException: 0x41b2ab80 <+0>: mflr r0 0x41b2ab84 <+4>: stw r31,-148(r1) 0x41b2ab88 <+8>: stw r30,-152(r1) 0x41b2ab8c <+12>: stw r0,4(r1) 0x41b2ab90 <+16>: stwu r1,-2992(r1) 0x41b2ab94 <+20>: mr r31,r1 . . . 0x41b2abe0 <+96>: stw r31,2844(r31) (which replaces the earlier save of the old Frame pointer R31 value with a copy of r1's current value. Note the offset relationships with the r1 adjustment: -2992+2844=3D-148) . . . 0x41b2add0 <+592>: lwz r31,2844(r31) (This restores the r1 value that resulted from the "stwu r1,-2992(r1)" = into R31.) . . . 0x41b2ae30 <+688>: lwz r31,-148(r1) (This restores the r1 value that resulted from the "stwu r1,-2992(r1)" = into R31.) . . . The wrong r31 value is present when _Unwind_RaiseException returns. But before that while _Unwind_RaiseException is active the C++ exception = handling infrastructure has been given bad r31 information for around = _Unwind_RaiseException's frame. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Mon Mar 7 20:00:03 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A73C6AC3673 for ; Mon, 7 Mar 2016 20:00:03 +0000 (UTC) (envelope-from peter.turay@vgtelecomreports.com) Received: from smtp.vgtelecomreports.com (smtp.vgtelecomreports.com [202.0.103.126]) by mx1.freebsd.org (Postfix) with ESMTP id 2CEF1EF0 for ; Mon, 7 Mar 2016 19:59:59 +0000 (UTC) (envelope-from peter.turay@vgtelecomreports.com) X-SmarterMail-Authenticated-As: admin@vgtelecomreports.com DomainKey-Signature: a=rsa-sha1; c=nofws; q=dns; d=vgtelecomreports.com; s=smtp; h=received:from:to:message-id:subject:date:mime-version:reply-to :content-type; b=hypxHS9besvzU/FrcM14D4GT0zEIdLVWW6r5KF0K5mD9cjAv1g7GpXdv9GQtr3SYD M2cxjnFcI0ninDOPT4NrwaqbQsaqT+inrVji3xP7ja7gyEG6sxhHNuIpTpMn4zCYT vp73d0Z7jdebRAFIyn1p99H0r9M/b2DuRtbZgESKc= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vgtelecomreports.com; s=smtp; h= content-type:reply-to:mime-version:date:subject:message-id:to:from; bh=0rzHUo6l9UqvF4kJ4y60KE+gtFmh+f5jBeXfvyOXlq8=; b=GC/fz3uNm+q2l5zGNx1waNdCAE+HxtyUD6rneI2JWX6Z8mRcawsgCpOgHOLWL4PIL 9XEhbAKmV3pv8yzYLNrWb+gq02YirrNamElDdHLRW8nOZnlpMvdDIbgRdLw/Hp1Nv f4gdjKExGhzUBTrgJcHd2F+PU2xebpvCB8VBsLn/o= Received: from WIN-ASQ29B6R1EP (WIN-ASQ29B6R1EP [202.0.103.127]) by smtp.vgtelecomreports.com with SMTP; Mon, 7 Mar 2016 17:07:37 +0000 From: Peter Turay To: freebsd-ppc@freebsd.org Message-Id: <20160307170737.1055945791@vgtelecomreports.com> Subject: Report - Internet Of Things (IOT) Market Forecast 2015-2020 Date: Mon, 7 Mar 2016 17:07:37 +0000 MIME-Version: 1.0 Reply-To: peter.turay@vgtelecomreports.com Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.21 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 Mar 2016 20:00:03 -0000 Internet Of Things (IOT) Market Forecast 2015-2020 Smart Home, Connected Transportation, Medical IoT, Industrial IoT & Others Telecomms Report Publication date: 9th March 2015 Number of Pages: 222 ------------------------------------------------------------ In the next five years, Visiongain expects to observe strong growth in IoT connections and revenue, driven by the increasing investment from private companies and a few government institutions that understand the dramatic effect that this technology will have in the global economy by 2020. Current developments in the Industrial and medical IoT technologies are expected to transform speed and ease of deployment, allowing much faster adoption rates and providing larger benefits to society. Contrastingly, Transportation IoT and other IoT initiatives (including Smart City) are not expected to grow at the same rate as Industrial or Medical IoT. Visiongain has analysed and segmented the five most important submarkets within global IoT market, providing a forecast for 2015-2020 for both connections and revenue. This 222 page report contains 213 tables, charts and figures providing a clear understanding of how the markets will evolve and which industries will reap the largest benefits from IoT. Our report also provides a forecast for regional revenues and the top 10 national IoT markets by connections. Additionally, we provide an overview of the Top 30 IoT companies with their USP offerings and their position in the IoT value chain. How the Internet of Things (IoT) Market Forecast 2015-2020: Smart Home, Connected Transportation, Medical IoT, Industrial IoT & Others report is worthwhile This report will be of value to current and future investors and key players in the technology market. Companies and operators with interest in developing new IoT services, launching services in new geographical regions, or looking to broaden their knowledge of this paradigm will immensely benefit here. Visiongain’s comprehensive analysis contains highly quantitative content delivering solid conclusions to aid your analysis further, and illustrate newer opportunities for greater ROI and competitiveness. Why you should buy the Internet of Things (IoT) Market Forecast 2015-2020: Smart Home, Connected Transportation, Medical IoT, Industrial IoT & Others Report • View global internet of things (IoT) market forecasts from 2015-2020 - Keep your knowledge ahead of your competition, whilst ensuring you exploit key business opportunities - Detailed projections of market connections and revenue, its competitors, and commercial drivers and restraints, allowing you to keep aware of key market factors. Alongside our market forecasts from 2015-2020, our new study shows, the latest developments in different verticals, original critical analysis, and insight into both national and global markets. • Internet of things (IoT) submarket forecasts from 2015-2020 - Industrial Internet of Things Connections 2015-2020 - Industrial Internet of Things Revenues 2015-2020 - Industrial Internet of Things 2015-2020: Agriculture - Industrial Internet of Things 2015-2020: Oil & Energy - Industrial Internet of Things 2015-2020: Retail - Industrial Internet of Things 2015-2020: Manufacturing & Others - Transportation Internet of Things Connections 2015-2020 - Transportation Internet of Things Revenues 2015-2020 - Transportation Internet of Things 2015-2020: Sea Transport - Transportation Internet of Things 2015-2020: Connected Cars - Transportation Internet of Things 2015-2020: Aviation - Smart Home Internet of Things Connections 2015-2020 - Smart Home Internet of Things Revenues 2015-2020 - Smart Home Internet of Things Connections 2015-2020: Smartphones - Smart Home Internet of Things Connections 2015-2020: Utilities - Other Internet of Things Revenues 2015-2020 (Including Fixed Broadband & Government) - Other Internet of Things Connections 2015-2020 (Including Fixed Broadband & Government) • Discover regional IoT revenue forecasts from 2015-2020 - What are the dynamics of the IoT industry? How will these markets expand? Which regions generate the most revenue? Use our forecasts and expert insight with 16 Charts and tables that provide clarity of the regional IoT markets, giving you more industry influence and opportunity for business growth. Discover where and how your organisation can succeed. Learn about the potential for each of these IoT regional markets with individual forecasts and analysis from 2015-2020. - European IoT revenue Forecast 2015-2020. - Asia Pacific IoT revenue Forecast 2015-2020. - North American Region IoT revenue Forecast 2015-2020. - Latin American Region IoT revenue Forecast 2015-2020. - Middle East & Africa Region IoT revenue Forecast 2015-2020. • Find connection forecasts for the Top 10 national markets from 2015-2020 - Chinese IoT Connections Forecasts 2015-2020 - United States IoT Connections Forecasts 2015-2020 - Japanese IoT Connections Forecasts 2015-2020 - Indian IoT Connections Forecasts 2015-2020 - Russian IoT Connections Forecasts 2015-2020 - German IoT Connections Forecasts 2015-2020 - Brazilian IoT Connections Forecasts 2015-2020 - Indonesian IoT Connections Forecasts 2015-2020 - United Kingdom IoT Connections Forecasts 2015-2020 - South Korean IoT Connections Forecasts 2015-2020 • Explore the factors affecting product developers and other stakeholders within the value chain. Learn about the forces influencing market dynamics. - Explore the economic, social, technological and regulatory issues assessing IoT advances. - Discover what the present and future outlook for business will be. Learn about the following business critical issues: - Regulatory constraints - Supply and demand dynamics - Competition from different companies - Increasing changes in the Telecoms sector - Different types of verticals and IoT services - Advances in product development - Analysis of barriers-to-entry - Increasing competition in the IoT market - The significance of government initiatives and support • Identify who the leading companies are in the IoT industry - Our report reveals the companies holding the greatest potential by exploring and analyzing the companies' commercial activities. View Visiongain’s assessment of the prospects for established competitors, rising companies and new market entrants. Our work defines the potential in helping you stay ahead. Acquire thorough understanding of the competitive landscape with profiles of 32 leading IoT companies examining their positioning, capabilities, product portfolios, R&D activity, services, focus, strategies and future outlook. - AT&T - Apple - Axeda - Berkeley Varitronics Systems - Cisco Systems - China Mobile - China Unicom - Deutsche Telekom - General Electric GE - Google - IBM - ILS Technology - iMetrik Solutions - Jasper Wireless - Kore Telematics - Microsoft - Novatel Wireless - NTT DoCoMo - Numerex - Orange - SensorLogic - Sierra Wireless - SIMCom Wireless Solutions - Sprint Corporation - Telecom Italia SpA - Telefónica S.A - TeliaSonera - Telit Wireless Solutions - Verizon Communications - Vodafone Group Plc - Wilson Electronics - Wyless Discover Information found nowhere else in this independent assessment of the IoT market The Internet of Things (IoT) Market Forecast 2015-2020: Smart Home, Connected Transportation, Medical IoT, Industrial IoT & Others provides impartial IoT sector analysis from independent business intelligence found only in our bespoke work. Our research provides you with key strategic advantages: informed forecasts, independent and objective analysis and company profiles, that provides you with substantial awareness over your competitors in the marketplace. What makes this report unique? Visiongain’s research methodology involves an exclusive blend of primary and secondary sources providing informed analysis. This methodology allows insight into the key drivers and restraints behind market dynamics and competitive developments. Furthermore, an ideal balance of qualitative analysis combined with extensive quantitative data is included, as well as global, national and regional markets forecasts from 2014-2019 Why choose Visiongain business intelligence? Visiongain’s increasingly diverse sector coverage strengthens our research portfolio. The growing cross-sector convergence and our interplay of game-changing technologies across numerous industries create new synergies, resulting in new business opportunities to leverage. How the Internet of Things (IoT) Market Forecast 2015-2020: Smart Home, Connected Transportation, Medical IoT, Industrial IoT & Others Report can benefit your business Visiongain's report is for anyone requiring analysis of the IoT market. You will discover market forecasts, technological trends, and predictions providing you with independent analysis derived from our extensive primary and secondary research. Discover more about the Internet-Of-Things market and find out who and where its future market prospects are. Order our report - The Internet of Things (IoT) Market Forecast 2015-2020: Smart Home, Connected Transportation, Medical IoT, Industrial IoT & Others. ------------------------------------------------------------ Table of Contents 1. Executive Summary 1.1 Internet of Things Could Revolutionize The Global Economy 1.2 Market Definition 1.3 Market Segmentation 1.4 Benefits of This Report 1.5 Methodology 1.6 Frequently Asked Questions (FAQ) 1.7 About Visiongain 2. Introduction to the Internet of Things Market 2.1 What Defines the Internet of Things? 2.2 M2M Technology is the Backbone behind the Massive Potential in the Internet of Things Market 2.2.1 M2M History and Recent Developments 2.3 A Benefits Derived From Internet of Things 2.4 IoT Applications by Industry 2.5 Cloud to Play Pivotal Role in the Internet of Things Industry Boom 2.6 Big-Data to Explode With the Rise in Internet of Things Market 2.7 Growth in the Wireless Sector 2.8 The Internet of Things Value Chain 3. Global Forecasts for IoT Revenues & Connections 2015-2020 3.1 Global Forecast for IoT Connections 2015-2020 3.2 Global IoT Revenue Forecast 2015-2020 4. Regional IoT Revenue Forecasts 2015-2020 4.1 North American Revenue Forecasts 2015-2020 4.2 LATAM Revenue Forecasts 2015-2020 4.3 European Revenue Forecasts 2015-2020 4.4 APAC Revenue Forecasts 2015-2020 4.5 MEA Revenue Forecasts 2015-2020 5. Internet of Things Sub-Segment Revenues & Connections Forecasts 2015-2020 5.1Global Forecasts for the Industrial Internet of Things Connections 2015-2020 5.1.1Global Forecasts for the Industrial Internet of Things Revenues 2015-2020 5.1.2 Global Forecasts for the Industrial Internet of Things 2015-2020: Agriculture 5.1.3 Global Forecasts for the Industrial Internet of Things 2015-2020: Oil & Energy 5.1.4 Global Forecasts for the Industrial Internet of Things 2015-2020: Retail 5.1.5 Global Forecasts for the Industrial Internet of Things 2015-2020: Manufacturing & Others 5.2 Global Forecasts for the Transportation Internet of Things Connections 2015-2020 5.2.1 Global Forecasts for the Transportation Internet of Things Revenues 2015-2020 5.2.2 Global Forecasts for the Transportation Internet of Things 2015-2020: Sea Transport 5.2.3 Global Forecasts for the Transportation Internet of Things 2015-2020: Connected Cars 5.2.4 Global Forecasts for the Transportation Internet of Things 2015-2020: Aviation 5.3 Global Forecasts for the Smart Home Internet of Things Connections 2015-2020 5.3.1 Global Forecasts for the Smart Home Internet of Things Revenues 2015-2020 5.3.2 Global Forecasts for the Smart Home Internet of Things Connections 2015-2020: Smartphones 5.3.3 Global Forecasts for the Smart Home Internet of Things Connections 2015-2020: Utilities 5.4 Global Forecasts for the Medical Internet of Things Connections 2015-2020 5.4.1 Global Forecasts for the Medical Internet of Things Connections 5.4.2 Global Forecasts for the Medical Internet of Things Revenues 5.4.2.1 Global Forecasts for the Medical Internet of Things Revenues 5.5 Global Forecasts for Other Internet of Things (Including Fixed 5.5.1 Global Forecasts for Other Internet of Things (Including Fixed 6. Top Ten National IoT Connections Forecasts 2015-2020 6.1 Chinese IoT Connections Forecasts 2015-2020 6.2 United States IoT Connections Forecasts 2015-2020 6.3 Japanese IoT Connections Forecasts 2015-2020 6.4 Indian IoT Connections Forecasts 2015-2020 6.5 Russian IoT Connections Forecasts 2015-2020 6.6 German IoT Connections Forecasts 2015-2020 6.7 Brazilian IoT Connections Forecasts 2015-2020 6.8 Indonesian IoT Connections Forecasts 2015-2020 6.9 United Kingdom IoT Connections Forecasts 2015-2020 6.10 South Korean IoT Connections Forecasts 2015-2020 7. Drivers & Constraints For The Internet of Things 7.1 Drivers of The Internet of Things 7.1.1 Cost savings 7.1.2 Creating New Revenue Streams 7.1.3 Connected Devices Growing Rapidly 7.1.4 IoT Gaining Popularity 7.1.5 Enhanced Market Segmentation 7.1.6 IoT Can be Expanded to Any Vertical 7.2 Constraints of The Internet of Things 7.2.1 IoT Solutions Can Be Expensive 7.2.2 Technical Problems 7.2.3 Limited Awareness 7.2.3 Limited Awareness 7.2.4 Security Concerns 7.2.5 Highly Fragmented Market Place 7.2.6 Unclear Business Models 8. Leading Companies in the Internet of Things Market 8.1 AT&T 8.1.1 AT&T Business Aims 8.1.2 AT&T Position In The Market 8.2 China Mobile Company Overview 8.2.1 China Mobile Historic Revenues & Net Income 8.2.3 China Mobile M2M Offerings 8.3 Vodafone Group Plc Overview 8.3.1 Vodafone Group Plc Historic Revenues & Net Income 8.3.2 Vodafone Group M2M Offerings 8.4 Deutsche Telekom Company Overview 8.4.1 Deutsche Telekom Historic Revenues & Net Income 8.4.2 Deutsche Telekom M2M Offerings 8.5 Telefónica S.A Overview 8.5.1 Telefónica S.A Historic Revenues & Net Income 8.5.2 Telefónica S.A M2M Products 8.6 Verizon Communications Overview 8.6.1 Verizon Communications Historic Revenues & Net Income 8.6.2 Verizon’s M2M Solutions and Overall Strategy 8.6.3 Verizon’s Focus on Automotive Industry 8.7 Orange S.A Overview 8.7.1 Orange S.A Historic Revenues & Net Income 8.7.2 Orange M2M Offerings 8.8 Sprint Corporation Overview 8.8.1 Sprint Corporation Historic Revenues & Net Income 8.8.2 Sprint’s Assets, Strengths, and Strategy 8.8.3 Sprint M2M Partner Ecosystem 8.9 Kore Telematics Overview 8.9.1 Kore Telematics Offerings 8.9.2 KORE Partnerships and Strategy Overview 8.10 NTT DoCoMo Overview 8.10.1 NTT DoCoMo Historic Revenues & Net Income 8.10.2 NTT DoCoMo M2M Offerings 8.11 Telecom Italia SpA Overview 8.11.1 Telecom Italia SpA Historic Revenues & Net Income 8.11.2 Telecom Italia SpA M2M Strategy 8.12 Wyless Total Revenues & M2M Connection 8.13 Axeda 8.14 SensorLogic 8.15 Sierra Wireless 8.16 Telit Wireless Solutions 8.16.1 Telit Wireless M&A 8.16.2 ILS Technology 8.17 TeliaSonera 8.18 Wilson Electronics 8.19 Novatel Wireless 8.20 SIMCom Wireless Solutions 8.21 Jasper Wireless 8.21.1 Jasper Wireless Control Center 8.21.2 Jasper Wireless-powered M2M alliance 8.22 Numerex 8.23 Berkeley Varitronics Systems 8.24 iMetrik Solutions 8.24.1 iMETRIK 8.24.2 iMetrik-COLLECT 8.24.3 iMetrik-COVER 8.24.4 iMetrik-PROTECT 8.25 IBM Company Overview 5.26 GE Company Overview 8.27 Microsoft Company Overview 8.27.1 Retail 8.27.2 Healthcare 8.27.3 Automotive 8.27.4 Microsoft Azure Intelligent Systems 8.28 Google Company Overview 8.29 Apple Inc. Overview 8.30 Cisco Systems Company Overview 8.31 Other Leading Companies in the IoT Market 9. Conclusions 9.1 Internet of Things Market Drivers 9.1.1 Network Coverage 9.1.2 Telematics and Telemetry Increasing Efficiency 9.1.3 Service Providers Need to Expand Offerings 9.1.4 IPv6 Will Increase IoT Opportunities 9.1.5 M2M Creating Scope for Development of New Applications 9.2 Internet of Things Characteristics 9.2.1 Fragmented Value Chain 9.2.2 Lack of Universal Standards 9.2.3 Marketing Challenges 9.2.4 Roaming 9.2.5 Security Concerns 9.3 Way Forward 9.3.1 Increase in M2M Partnerships 9.3.2 Standardisation 9.3.3 Measuring Data 9.3.4 New Business Models 10. Glossary ------------------------------------------------------------ List of Tables Table 2.1: IoT Applications by Industry Table 3.1: Global IoT Connections Forecast 2015-2020 (Billions, AGR % and CAGR) Table 3.2: Global IoT Sub-Segment Connections Forecast 2015-2020 (Billions, AGR%) Table 3.6: Global IoT Revenues Forecast 2015-2020 ($ B, AGR %, CAGR and Cumulative Revenues) Table 3.7: Global IoT Sub-Segment Revenues Forecast 2015-2020 ($ B, AGR % and Cumulative Revenues ) Table 4.1: Regional IoT Revenue Forecast 2015-2020 ($ Billions, AGR%, % Share) Table 4.4: North American Revenue Forecast 2015-2020 ($ Billions, AGR%, Cumulative Revenues) Table 4.7: LATAM IoT Revenue Forecast 2015-2020 ($ Billions, AGR%, Cumulative Revenues) Table 4.10: European IoT Revenue Forecast 2015-2020 ($ Billions, AGR%, Cumulative Revenues) Table 4.13: APAC IoT Revenue Forecast 2015-2020 ($ Billions, AGR%, Cumulative Revenues) Table 4.16: MEA IoT Revenue Forecast 2015-2020 ($ Billions, AGR%, Cumulative Revenues) Table 5.1: Industrial IoT Connections Forecast 2015-2020 (Millions, AGR % and CAGR) Table 5.2: Industrial IoT Connections by Industry Forecast 2015-2020 (Millions, IIoT AGR )Table 5.6: Industrial IoT Revenues Forecast 2015-2020 ($ Billions, AGR %, Cumulative Revenues and CAGR) Table 5.16: Addressable Plants, Assets and Machinery within the Energy Industry 2015 Table 5.22: Addressable Plants, Assets and Machinery within the Manufacturing Industry 2015 Table 5.23: Total Transportation Fleet and Total IoT Connected Fleet Forecast 2015-2020 (Millions, AGR % and CAGR)Table 5.27: Transportation IoT Revenues Forecast 2015-2020 ($ Billions, AGR %, Cumulative Revenues and CAGR) Table 5.53: Smart Home IoT Connections Forecast 2015-2020 (Millions, AGR % and CAGR) Table 5.54: Smart Home IoT Connections Forecast by Segment 2013-2020 (Millions, AGR % and CAGR) Table 5.59: Smart Home IoT Revenues Forecast 2015-2020 ($B, AGR %, Cumulative Revenues and CAGR) Table 5.63: Smartphones Connections Forecast 3G vs. 4G 2013-2020 (Millions, AGR %) Table 5.68: Smart Home Energy & Utilities Connections Forecast Smart Meter vs. Other 2013-2020 (Millions, AGR %) Table 5.72: Medical IoT Connections Forecast 2015-2020 (Millions, AGR % and CAGR) Table 5.77: Most Important Factors Driving Healthcare Costs Up Table 5.79: Medical IoT Revenues Forecast 2015-2020 ($ b, AGR %, Cumulative and CAGR) Table 5.83: Main Healthcare Conditions Related to Different Telemedicine Technologies Table 5.86: Other IoT Connections Forecast 2015-2020 (Millions, AGR % and CAGR) Table 5.90: Other IoT Revenue Forecast 2015-2020 (Millions, AGR %, Cumulative Revenues and CAGR) Table 6.1: Top 10 National IoT Connections Forecast 2015-2020 (Millions, AGR%, % Share) Table 6.3: Chinese IoT Connections Forecast 2015-2020 (Millions, AGR%, CAGR) Table 6.6: US IoT Connections Forecast 2015-2020 (Millions, AGR%, CAGR) Table 6.9: Japanese IoT Connections Forecast 2015-2020 (Millions, AGR%, CAGR) Table 6.12: Indian IoT Connections Forecast 2015-2020 (Millions, AGR%, CAGR) Table 6.15: Russian IoT Connections Forecast 2015-2020 (Millions, AGR%, CAGR) Table 6.18: German IoT Connections Forecast 2015-2020 (Millions, AGR%, CAGR) Table 6.21: Brazilian IoT Connections Forecast 2015-2020 (Millions, AGR%, CAGR) Table 6.24: Indonesian IoT Connections Forecast 2015-2020 (Millions, AGR%, CAGR) Table 6.27: UK IoT Connections Forecast 2015-2020 (Millions, AGR%, CAGR) Table 6.30: South Korean IoT Connections Forecast 2015-2020 (Millions, AGR%, CAGR) Table 8.1 AT&T Inc. Company Overview 2015 (Total Revenue 2014, Net Profit, Total Employees, CEO, HQ, Ticker and, Website) Table 8.2: AT&T Total Revenues and Net Income 2008-2014 (Revenues in $b &AGR %) Table 8.4: AT&T M2M Solution, Assets, and Advantages Table 8.5 China Mobile Company Overview 2015 (Total Revenue2014, Total Company Net Income, Employees, CEO, HQ, Ticker and, Website) Table 8.6: China Mobile Total Revenues and Net Income 2008-2014 (Revenues in $b and AGR %) Table 8.8: Sprint M2M Solutions and Leading Verticals Table 8.9 Vodafone Group Plc Overview 2015 (Total Revenue, Net Profit, Employees, CEO, HQ, Ticker, Website) Table 8.10: Vodafone Total Revenues and Net Income 2008-2014 (Revenues in $b & AGR %) Table 8.12: Key Features and Benefits of Vodafone’s M2M Solution Table 8.13: Deutsche Telekom Company 2015 (Total Revenue, Net Profit, ,Total Employees, CEO, HQ, Ticker and, Website) Table 8.14: Deutsche Telekom Total Revenues and Net Income 2008-2014 (Revenues in $b & AGR %) Table 8.16: Deutsche Telekom M2M Solution Table 8.17: Telefónica S.A. Overview 2015 (Total Revenue 2014, Net Profit, Total Employees, CEO, HQ, Ticker and, Website) Table 8.18: Telefónica Total Revenues and Net Income 2008-2014 (Revenues in $b and AGR %) Table 8.20 Verizon Communications Overview 2015 (Total Revenue 2014, Net Profit, Total Employees, CEO, HQ, Ticker and, Website) Table 8.21: Verizon Total Revenues and Net Income 2008-2014 (Revenues in $b and AGR %) Table 8.22: Verizon’s M2M Solutions Table 8.23: Orange Overview 2015 (Total Revenue2014, Employees, CEO, HQ, Ticker, Contact, Website) Table 8.24: Total Revenues and Net Income 2008-2014 (Revenues in $b and AGR %) Table 8.26: Orange M2M Core Offerings Table 8.27: Orange M2M Use Cases Table 8.28: Sprint Corporation Overview 2015 (Total Revenue 2014, Net Profit, Total Employees, CEO, HQ, Ticker and, Website) Table 8.29: Sprint Total Revenues and Net Income 2008-2014 (Revenues in $b and AGR %) Table 8.31: Sprint M2M Solutions and Leading Verticals Table 8.32: Kore Telematics Overview 2015 (Total Revenue 2014 $b, Total M2M Subscriptions M, Global M2M Subscriptions Share %, Employees, CEO, HQ, Website) Table 8.33: KORE Telematics M2M Connectivity Services Table 8.34: NTT DoCoMo Overview 2015 (Total Revenue 2014 $b, Net Profit, Total Employees, CEO, HQ, Ticker and, Website) Table 8.35: DoCoMo Total Revenues and Net Income 2009-2014 (Revenues in $b & AGR %) Table 8.37: NTT DoCoMo M2M Offerings Table 8.38: Telecom Italia SpA Telecommunications Company Overview 2015 (Total Revenue 2014 $b, Net Profit, Total Employees, CEO, HQ, Ticker and, Website) Table 8.39: Telecom Italia SpA Telecommunications Total Revenues and Net Income 2009-2014 (Revenues in $b and AGR %) Chart 8.40: Telecom Italia SpA Total Revenues and Net Income 2009-2014 (Revenues in $b and AGR %) Table 8.43: SIMCom M2M Use Cases Table 8.44: Numerex Company Overview 2015 (Total Revenue 2014 m, Net Profit m, , Total Employees, CEO, HQ, Ticker and, Website) Table 8.45 iMetrik M2M Services Table 8.46 iMetrik -PROTECT Table 8.47: IBM Company Overview 2015 (Total Revenue, Revenue from Internet of Things, % Revenue From Internet of Things, Global Market Share %, HQ, Ticker, Contact, Website) Table 8.49: IBM Adept Performance Management Solution Focus Areas Table 8.50: GE Company Overview 2015 (Total Revenue, , Global Market Share %, HQ, Ticker, Contact, Website) Table 8.51: Microsoft Company Overview 2015 (Total Revenue, Revenue from Internet of Things, % Revenue From Internet of Things, Global Market Share %, HQ, Ticker, Contact, Website) Table 8.53: Windows Embedded Product Portfolio Table 8.54: Google Company Overview 2015 (Total Revenue, HQ, Ticker, Contact, Website) Table 8.55: Apple Company Overview 2015 (Total Revenue, HQ, Ticker, Contact, Website) Table 8.56: Cisco Company Overview 2015 (Total Revenue, Revenue from Internet of Things, % Revenue From Internet of Things, Global Market Share %, HQ, Ticker, Contact, Website) Table 8.57: Other Leading Companies in the M2M Market 2015 (Company, Product /service) ------------------------------------------------------------ List of Figures Figure 1.1: Internet of Things Market Segmentation Figure 2.2: IoT Value Chain Figure 8.48: IBM MessageSight System Figure 8.52: Microsoft Azure Intelligent Systems ------------------------------------------------------------ List of Charts Chart 3.3: Global IoT Connections Sub-Segment Share 2015-2018-2020 (% of Total Connections) Chart 3.4: Global IoT Connections Sub-Segment Forecast 2015-2020 (Billions, Total IoT AGR % ) Chart 3.5: IoT AGR% for Connections Sub-Segment Forecast 2015-2020 (AGR %) Chart 3.8: Global IoT Sub-Segment Revenues 2015-2018-2020 (% of Total Revenues) Chart 3.9: Global IoT Sub-Segment Revenues Forecast 2015-2020 ($ B, Total IoT AGR % ) Chart 3.10: IoT Revenue AGR% Sub-Segment Forecast 2015-2020 (AGR %) Chart 4.2: Regional IoT Revenue Forecast 2015-2020 ($ Billions, Global AGR %) Chart 4.3: Regional IoT Revenue Share 2015-2018-2020 (%) Chart 4.5: North American Revenue Forecast 2015-2020 ($ Billions, AGR%) Chart 4.6: North American Revenue Share of Global IoT 2015-2018-2020 (% Share) Chart 4.8: LATAM IoT Revenue Forecast 2015-2020 ($ Billions, AGR%) Chart 4.9: LATAM Revenue Share of Global IoT 2015-2018-2020 (% Share) Chart 4.11: European IoT Revenue Forecast 2015-2020 ($ Billions, AGR%) Chart 4.12: European Revenue Share of Global IoT 2015-2018-2020 (% Share) Chart 4.14: APAC IoT Revenue Forecast 2015-2020 ($ Billions, AGR%) Chart 4.15: APAC Revenue Share of Global IoT 2015-2018-2020 (% Share) Chart 4.17: MEA IoT Revenue Forecast 2015-2020 ($ Billions, AGR%) Chart 4.18: MEA Revenue Share of Global IoT 2015-2018-2020 (% Share) Chart 5.3: Industrial IoT Connections by Industry Forecast 2015-2020 (% ) Chart 5.4: Industrial IoT Connections Forecast by Industry 2015-2020 (Millions, AGR %) Chart 5.5: Industrial IoT Share of Total IoT Connections 2015-2018-2020 (%) Chart 5.7: Industrial IoT Revenues Forecast 2015-2020 ($ Billions, AGR %) Chart 5.8: Industrial IoT Share of Total IoT Revenues 2015-2018-2020 (%) Chart 5.9: Total Number of Connections Within The Agricultural Industry Forecast By Technology 2015-2020 (Millions, AGR %) Chart 5.10: Breakdown of Total Number of Connections Within The Agricultural Industry 2015-2018-2020 (%) Chart 5.11: Share of Top 10 Countries Within the Global Dairy Cows Market 2015 (% of Total Dairy Cows) Chart 5.12: Share of Top 6 Countries Within the Global Cattle Market 2015(% of Total Global Cattle) Chart 5.13: Share of farms by Regional and Socio-Economic Breakdown (% of Global Farms) Chart 5.14: Agriculture Share of Industrial IoT Connections 2015-2018-2020 (%) Chart 5.15: Energy Share of Industrial IoT Connections 2015-2018-2020 (%) Chart 5.16: Total Industrial IoT Connections within the Energy Industry Forecast 2015-2020(Millions, Total Industrial IoT AGR%, Oil & Energy AGR % Chart 5.18: Retail Share of Industrial IoT Connections 2015-2018-2020 (%) Chart 5.19: Industrial IoT Connections Within Retail Forecast by Application 2015-2020 (Millions, AGR %) Chart 5.20: Industrial IoT Connections Within Retail Forecast by Application 2015-2018-2020 ( Chart 5.21: Total Industrial IoT Connections within the Manufacturing Industry Forecast 2015-2020 (Millions, Total IIoT AGR%, Manufacturing AGR % Chart 5.24: Total Transportation & Total Connected Fleet Forecast 2015-2020 (Millions, AGR %) Chart 5.25: Transportation IoT Connections Breakdown Forecast 2015-2020 (Millions, AGR %) Chart 5.26: Transportation Share of Total IoT Connections 2015-2018-2020 (%) Chart 5.28: Transportation IoT Revenues by Transportation Type Forecast 2015-2020 ($ billions)) Chart 5.29: Transportation IoT Revenues by Transport Type Forecast 2015-2018-2020 (% Share) Chart 5.30: Transportation Share of Total IoT Revenues 2015-2018-2020 (%) Chart 5.31: Total Number of Active Ships and Container Fleet Forecast 2015-2020 (Ships in 000’s, Containers in Millions) Chart 5.32: Breakdown of Active Ships by Type 2015 (%) Chart 5.33: Breakdown of Active Ships by Type 2015 (000’s) Chart 5.34: Breakdown of Active Containers by Type 2015 (% Share and TEUs Millions) Chart 5.35: Total Number of Maritime Connections and Revenues Forecast 2015-2020 (Connections in Millions, $ B) Chart 5.36: Ships Connected as a Percentage of Total Maritime Connections 2015-2018-2020 (%) Chart 5.37: Connected Sea Fleet Share of Total Transportation IoT Connections 2015-2018-2020 (%) Chart 5.38: Connected Sea Fleet Share of Total Transportation IoT Revenues 2015-2018-2020 (%) Chart 5.39: Total Number of Active Passenger and Commercial Vehicles Forecast 2015-2020 (Millions, AGR) Chart 5.40: Total Number of Connected and Non-Connected Vehicles Forecast 2015-2020 (Millions, AGR) Chart 5.41: Connected Passengers & Commercial Vehicles Share of Total Transportation IoT Connections 2015-2018-2020 (%) Chart 5.42: Global Connected Passengers & Commercial Vehicles Share of Global Connected Cars 2015-2018-2020 (%) Chart 5.43: Connected Passengers vs. Connected Commercial Vehicles Revenue Forecast 2015-2020 ($ B , AGR %) Chart 5.44: Connected Vehicles Forecast Share: Commercial vs. Passenger 2015-2018-2020 ( %) Chart 5.45: Connected Commercial and Passenger Cars Share of Total Transportation IoT Revenues 2015-2018-2020 (%)Chart 5.46: Total Number of Active Aircrafts Forecast 2015-2020 (000’s, AGR%) Chart 5.47: Total Number of Active Aircrafts By Type 2015 (000’s, %) Chart 5.48: Share of Total Active Hours By Type of Aircraft t 2015 (%) Chart 5.49: Total Number of Active Aircraft and Air Transport IoT Connections Forecast 2015-2020 (Aircrafts in 000’s, Connections in Millions) Chart 5.50: Connected Air Fleet as a Share of Total Transportation IoT Connections 2015-2018-2020 (%)Chart 5.51: Total Number of Connected Aircraft Revenues Forecast 2015-2020 ($ Billions, AGR %) Chart 5.52: Connected Aircrafts Share of Total Transportation IoT Revenues 2015-2018-2020 (%) Chart 5.55: Smart Home IoT Connections Forecast 2013-2020 (Millions, AGR %) Chart 5.56: Smart Home Share of Total IoT Connections 2015-2018-2020 (%) Chart 5.57: Smart Home IoT Connections Forecast by Sub-Segment 2013-2020 (Millions) Chart 5.58: Smart Home IoT Connections Forecast by Sub-Segment 2015-2018-2020 (%) Chart 5.60: Smart Home IoT Revenues Forecast 2015-2020 ($B, AGR %) Chart 5.61: Smart Home Share of Total IoT Revenues 2015-2018-2020 (%) Chart 5.62: Smartphones Share of Total Smart Home Connections 2015-2018-2020 (%) Chart 5.64: Smartphone Connections Forecast 3G vs. 4G 2013-2020 (Millions) Chart 5.65: Smartphone Connections Forecast 3G vs. LTE vs. LTE-Advanced 2015-2020 (Millions) Chart 5.66: Smartphone Connections Forecast 3G vs. LTE vs. LTEA 2015-2018-2020 (%) Chart 5.67: Total MNOs Service Revenue Forecast 2015-2020 2G vs. 3G vs. 4G ($ Billions) Chart 5.69: Smart Home Energy & Utilities IoT Connections Forecast 2013-2020 (Millions, AGR %) Chart 5.70: Smart Home Energy & Utilities Connections Forecast Smart Meters vs Other 2013-2020 (Millions, AGR %) Chart 5.71: Global Smart Home Energy & Utilities Share of Total Smart Home Connections , Smart Meters vs. Smart Energy vs. Other 2015-2018-2020 (%)Chart 5.73: Medical IoT Share of Total IoT Connections 2015-2018-2020 (%) Chart 5.74: Medical IoT Connections Forecast 2015-2020 (Millions, AGR %) Chart 5.75: Regional Medical IoT Connections Forecast 2015-2020 (Millions, AGR %) Chart 5.76: Regional Medical IoT Connections Forecast 2015-2018-2020 (%) Chart 5.78: M-Health and Fitness & Activity Trackers Shipments Forecast 2015-2020 (Trackers in Millions, M-Health in Thousands) Chart 5.80: Medical IoT Share of Total IoT Revenues 2015-2018-2020 (%) Chart 5.81: Global Medical IoT Revenues Forecast 2015-2018-2020 (%) Chart 5.82: Telemedicine Revenues Forecast By Sub Segment 2015-2020 ($ B, AGR %) Chart 5.84: Chart 5.84: Telemedicine Revenues Forecast By Healthcare Condition 2015-2018-2020 (%) Chart 5.87: Other IoT Connections Forecast 2015-2020 (Millions, AGR %) Chart 5.88: Other IoT Connections Forecast by Type 2015-2018-2020 (%) Chart 5.89: Others IoT Share of Total IoT Connections 2015-2018-2020 (%) Chart 5.91: Other IoT Revenues Forecast 2015-2020 ($ B, AGR %) Chart 5.92: Other IoT Revenues Forecast by Type 2015-2018-2020 (%) Chart 5.94: Urbanisation Rate Forecast Urban vs. Rural Population 1950-2040 (Billion, Urbanisation Rate %) Chart 5.95: Others IoT Share of Total IoT Revenues 2015-2018-2020 (%) Chart 6.2: Top 10 National IoT Connections Forecast 2015-2020 (Millions, AGR%) Chart 6.4: Chinese IoT Connections Forecast 2015-2020 (Millions, AGR%) Chart 6.5: Chinese Share of Global IoT Connections Forecast 2015-2018-2020 (%) Chart 6.7: US IoT Connections Forecast 2015-2020 (Millions, AGR%) Chart 6.8: US Share of Global IoT Connections Forecast 2015-2018-2020 (%) Chart 6.10: Japanese IoT Connections Forecast 2015-2020 (Millions, AGR%) Chart 6.11: US Share of Global IoT Connections Forecast 2015-2018-2020 (%) Chart 6.13: Indian IoT Connections Forecast 2015-2020 (Millions, AGR%) Chart 6.14: Indian Share of Global IoT Connections Forecast 2015-2018-2020 (%) Chart 6.16: Russian IoT Connections Forecast 2015-2020 (Millions, AGR%) Chart 6.17: Russian Share of Global IoT Connections Forecast 2015-2018-2020 (%) Chart 6.19: German IoT Connections Forecast 2015-2020 (Millions, AGR%) Chart 6.20: Russian Share of Global IoT Connections Forecast 2015-2018-2020 (%) Chart 6.22: Brazilian IoT Connections Forecast 2015-2020 (Millions, AGR%) Chart 6.23: Brazilian Share of Global IoT Connections Forecast 2015-2018-2020 (%) Chart 6.25: Indonesian IoT Connections Forecast 2015-2020 (Millions, AGR%) Chart 6.26: Indonesian Share of Global IoT Connections Forecast 2015-2018-2020 (%) Chart 6.28: UK IoT Connections Forecast 2015-2020 (Millions, AGR%) Chart 6.29: UK Share of Global IoT Connections Forecast 2015-2018-2020 (%) Chart 6.31: South Korean IoT Connections Forecast 2015-2020 (Millions, AGR%) Chart 6.32: South Korean Share of Global IoT Connections Forecast 2015-2018-2020 (%) Chart 8.3: AT&T Total Revenues and Net Income 2008-2014 (Revenues in $b and Net Income AGR %) Chart 8.7: China Mobile Total Revenues and Net Income 2008-2014 (Revenues in $b and Net Income AGR %) Chart 8.15: Deutsche Telekom Total Revenues and Net Income 2008-2014 (Revenues in $b and Net Income AGR %) Chart 8.19: Telefónica Total Revenues and Net Income 2008-2014 (Revenues in $b and Net Income AGR %) Chart 8.21: Verizon Total Revenues and Net Income 2008-2014 (Revenues in $b and Net Income AGR %) Chart 8.25: Orange Total Revenues and Net Income 2008-2014 (Revenues in $b & Net Income AGR%) Chart 8.30: Sprint Total Revenues and Net Income 2008-2014 (Revenues in $b & Net Income AGR %) Chart 8.36: DoCoMo Total Revenues & Net Income 2008-2014 (Revenues in $b & Net Income AGR %) Chart 8.41: Wyless Total M2M Connections 2012-2014 Connections in Millions, AGR %) Chart 8.42: Wyless Total M2M Revenues 2012-2014 ($ Billions, AGR %) -------------------------------------------- Companies Mentioned in this report 7 Layers Adept Enterprise Solutions Aeris Communications Aeroscout AFrame Digital Alcatel-Lucent Alien Technology America Movil Apple Inc Arkessa Arrayent Arrow Electronics AT&T Atos Origin SA Audi Augusta Systems AVIDwireless Axeda Berkeley Varitronics Systems Best Buy Boston Dynamics CalAmp CETECOM China Mobile China Mobile Internet of Things Ltd Cinterion Cisco Systems Claro Americas Clearconnex Coca-Cola Comtrol Connect One Connected Development Coronis CrossBridge Solutions DataOnline DataRemote DeepMind Deutsche Telekom Digi International DigiCore Drive.Cam Dust Networks Echelon eDevice EE EE (Everything Everywhere) ei3 Ember Enfora Ericsson Esprida Etisalat Eurotech Exosite Feeney Wireless Ford Motor Company Fusion Wireless Gemalto General Electrics (GE) General Motors Globalstar Google Honeywell International Huawei Hughes Telematics IBM ILS Technology iMETRIK iMetrik Solutions Inilex Inmarsat Intel Iridium Communications Itron IWOW Janus Remote Communications Jasper Technologies Jasper Wireless Inc Kleiner Perkins Caufield & Byers (KPCB) KORE Telematics KPN Laird Technologies Lantronix Lenovo LG M2M Air M2M Communications M2M DataSmart Marvell MEMSIC Micro Technologies Microchip Technology Microsoft Millenial Net Mobilkom Australia Mocana Morey Motorola MOXA NeoWay Nest Labs Nokia solutions & Networks Norwest Venture Partners Novatel Wireless Inc. nPhase NTT DOCOMO Numerex Omnilink Systems OnStar Optus Business Oracle Orange Business Services (OBS) Orange SA ORBCOMM Palantiri Systems Panasonic Pedigree Technologies Perle Systems Post Luxembourg Group Precidia Technologies Qualcomm Quecklink Wireless Solutions Quectel Red Bend Software RF Code Inc. RF Monolithics Rogers Communications RRE Sagemcom Savi Technology SENA Technologies SensorLogic Sierra Wireless Inc. Sigma Designs SIM Technology Group LTD SIMCom Wireless Solutions Singtel Sixnet SkyTel Sony Sprint Corporation Swisscom Synchronoss Technologies Tech Mahindra Ltd Telcel Telecom Italia Telefonica S.A Telefonica UK Telekom Austria Telenor ASA Telenor Connexion Telenor Objects TeliaSonera Telit Communications Telit Wireless Telstra Telular TELUS Mobility Tendril Networks Texas Instruments ThingMagic TIM TMData T-Mobile Tokyo Electric Power Company (TEPCO) Top Global Tridium Trimble Tyntec ublox u-Blox V2COM Verizon Communications Vimpelcom Vivo Vodafone Group Plc Volkswagen Walsh Wireless WebTech Wireless Wilson Electronics Wipro Wyless Group Xact Technology Xata ZTE Other Organisations Mentioned in this Report Brazilian telecommunications regulator Agência Nacional de Telecomunicações (Anatel) DECC EU Casagras Global M2M Association (GMA) MIT OECD Technology Association of Georgia The Alliance for Telecommunications Industry Solutions (ATIS) of the U.S The Association of Radio Industries and Businesses (ARIB) and the Telecommunication Technology Committee (TTC) of Japan The China Communications Standards Association (CCSA) The European Telecommunications Standards Institute (ETSI) The Telecommunications Industry Association (TIA) of the U.S. The Telecommunications Technology Association (TTA) of Korea ------------------------------------------------------------ Pricing Single User License: Single user copies of this report are available for EUR2249/ USD2699/ GBP1099 Departmental License: Entitles up to 5 individual users to access this report for EUR3599/ USD4499/ GBP2999 (Not suitable for library usage) Site License: Allow your company to have access to this report at one location for EUR5999/ USD7499/ GBP4999 (Suitable for library storage and use) Global License: Have your whole company worldwide to access this information for EUR8399/ USD9999/ GBP6999 ------------------------------------------------------------ Ordering To order this report, contact Peter Turay on: Telephone: +44(0)207 549 0537 or email: peter.turay@vgtelecomreports.com And provide the following information: Report Title: Report License (Single User/Departmental/Site/Global): Name: User Email: Job Title: Company: Invoice Address: Telephone and Fax number: EEC VAT Number (only for E.U.): Please contact me should you have any questions or wish to receive an executive summary of this report. I look forward to hearing from you. Best Regards, Peter Turay Telecoms Industry Consultant Terms and Conditions By replying to this e-mail submitting your order for this product you have agreed without limitation or qualification to be bound by and to comply with these Terms and Conditions. You agree that you will not fail to complete any transaction after submitting an order to purchase a product or submit any order to purchase a product where you do not intend to complete the transaction. Management Reports will only be sent on receipt of payment. You are currently subscribed to this list as freebsd-ppc@freebsd.org . As a valued contact or customer, you are receiving this email with information that we believe will be relevant to you. If however, you wish to stop future messages, please reply to this email typing "REMOVE" in the subject box. Registered Office: BSG House, 230 City Road, London, EC1V 2QY, U.K. Campaign Enterprise Uses Arial Software Technology From owner-freebsd-ppc@freebsd.org Tue Mar 8 14:00:58 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A7EECAC7C03 for ; Tue, 8 Mar 2016 14:00:58 +0000 (UTC) (envelope-from admin@www.doska.ru) Received: from vm9851.vps.agava.net (vm9851.vps.agava.net [IPv6:2a03:4900:2:653::2]) (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 6BEADDC3 for ; Tue, 8 Mar 2016 14:00:58 +0000 (UTC) (envelope-from admin@www.doska.ru) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=www.doska.ru; s=dkim; h=Sender:Content-Transfer-Encoding:Content-Type:MIME-Version:Date:Subject:To:From:Message-ID; bh=8+Zx9c2sLjDOVQQmYYIfsPYt+gd8MdgykU+11L7VP8M=; b=pMf5yka1P88OBxclCxBkK1ozJ85LjTzk77hL0rXkuwtrqRRsbP5t3G7ntPlG14iweYElVqbWlpzNqmRvq8EIyxj8/CgvUv3npFK9wfYbqxFEZKVuut+bFWcO6WqFVxHklzgHDsmYDUNU7W/HfgLvA5ObvDZ7exYv++fgCl8A8GA=; Received: by vm9851.vps.agava.net with esmtpa (Exim 4.72) id 1adIC0-00074P-CF; Tue, 08 Mar 2016 17:00:56 +0300 Message-ID: <619BD26200D4F300DCD99020B4A68D77@adfojajdgvfuaewyediwBHDUASFI> From: "admin" <349599@ukr.net> To: Subject: =?windows-1251?B?3evl6vLw7u3t++Ug4ejn7eXxIPHv8ODi7vft?= =?windows-1251?B?6OroIOgg4eDn+yDk4O3t+/U=?= Date: Tue, 8 Mar 2016 16:03:20 +0200 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Windows Live Mail 15.4.3538.513 X-MimeOLE: Produced By Microsoft MimeOLE V15.4.3538.513 Sender: admin@www.doska.ru MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1251" X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.21 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 Mar 2016 14:00:58 -0000 From owner-freebsd-ppc@freebsd.org Tue Mar 8 15:00:23 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C1B4AAC7DDB for ; Tue, 8 Mar 2016 15:00:23 +0000 (UTC) (envelope-from admin@infosliv.club) Received: from vm9850.vps.agava.net (vm9850.vps.agava.net [80.78.243.68]) (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 6B92E257 for ; Tue, 8 Mar 2016 15:00:23 +0000 (UTC) (envelope-from admin@infosliv.club) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infosliv.club; s=dkim; h=Sender:Content-Type:MIME-Version:Date:Subject:To:From:Message-ID; bh=+Wsd3gOFHtv6Thf+jqn8i+ghdT+Z1wyh7HVooXD4NYM=; b=n+olLOQF3EqXmoWHfT290Rc2DTDa6k9fbcE48djJXHR3MzFFcHfnBI9S6gJZZibd/tvhdzVmgbzKKS1e4GKlMuQ7RNb28ycpbnI2z1LfgqIWuMla6NFoMx4o/ZiKsQqDc8+EXxh0IBBmEBcYiD/P2cE39a1360fbBOZiDF3zyiQ=; Received: by vm9850.vps.agava.net with esmtpa (Exim 4.72) id 1adJ6U-0007nT-7G; Tue, 08 Mar 2016 17:59:18 +0300 Message-ID: <51ABE25230E4C5865A5F16A6321167DC@adfojajdgvfuaewyediwBHDUASFI> From: "admin" <932082@ukr.net> To: Subject: =?windows-1251?B?0OXq6+Ds4CDC4Pjl4+4g4ejn7eXx4CDo6+gg?= =?windows-1251?B?8/Hr8+Mg7+4g4+7w7uTg7CDT6vDg6O37?= Date: Tue, 8 Mar 2016 17:01:41 +0200 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Windows Live Mail 16.4.3528.331 X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3528.331 Sender: admin@infosliv.club Content-Type: text/plain; charset="windows-1251" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.21 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 Mar 2016 15:00:23 -0000 =C7=E4=F0=E0=E2=F1=F2=E2=F3=E9=F2=E5! =CF=F0=E5=E4=EB=E0=E3=E0=E5=EC =F3=F1=EB=F3=E3=E8 =EF=EE =E4=EE=F1=F2=E0=E2= =EA=E5 =FD=EB=E5=EA=F2=F0=EE=ED=ED=EE=E9 =EF=EE=F7=F2=FB =EF=EE =EE=E1=EB= =E0=F1=F2=ED=FB=EC =E3=EE=F0=EE=E4=E0=EC =D3=EA=F0=E0=E8=ED=FB. =CA=EE=EB=E8=F7=E5=F1=F2=E2=E0 =E0=E4=F0=E5=F1=E0=F2=EE=E2 =EC=EE=E3=F3=F2= =EE=F2=EB=E8=F7=E0=F2=F1=FF =EE=F2 =F3=EA=E0=E7=E0=ED=ED=FB=F5 =E2 =F2=E0= =E1=EB=E8=F6=E5 =E2 =E7=E0=E2=E8=F1=E8=EC=EE=F1=F2=E8 =EE=F2 =EE=E1=ED=EE= =E2=EB=E5=ED=E8=E9, =EF=F0=E8 =EA=E0=E6=E4=EE=EC =E7=E0=E1=F0=EE=F8=E5=ED=ED=FB=E5 =FF=F9=E8=EA= =E8 =F3=E4=E0=EB=FF=FE=F2=F1=FF =E8 =E4=EE=E1=E0=E2=EB=FF=FE=F2=F1=FF =ED= =EE=E2=FB=E5. =D2=E0=EA =E6=E5 =EF=F0=EE=E2=EE=E4=E8=EC =F0=E0=F1=F1=FB=EB=EA=E8 =EF=EE= =F1=F2=F0=E0=ED=E0=EC =D1=CD=C3 =E8 =E7=E0=F0=F3=E1=E5=E6=FC=FF (=EA=EE=EB= =E8=F7=E5=F1=F2=E2=EE =E8 =F1=F2=EE=E8=EC=EE=F1=F2=FC =F3=F2=EE=F7=ED=FF=E9= =F2=E5). =CD=E0=F1=E5=EB=E5=ED=ED=FB=E9 =EF=F3=ED=EA=F2 =CA=EE=EB=E8=F7=E5=F1=F2=E2= =EE\=F1=F2=EE=E8=EC=EE=F1=F2=FC=CE=E1=EB=E0=F1=F2=FC =CA=EE=EB=E8=F7=E5=F1= =F2=E2=EE\=F1=F2=EE=E8=EC=EE=F1=F2=FC =C2=C8=CD=CD=C8=D6=C089426 - 250 =E3=F0=ED.=C2=E8=ED=ED=E8=F6=EA=E0=FF =EE= =E1=EB=E0=F1=F2=FC125375 - 350 =E3=F0=ED =C4=CD=C5=CF=D0=CE=CF=C5=D2=D0=CE=C2=D1=CA140749 - 350 =E3=F0=ED=C4=ED=E5= =EF=F0=EE=EF=E5=F2=F0=EE=E2=F1=EA=E0=FF =EE=E1=EB=E0=F1=F2=FC210648 - 400= =E3=F0=ED =C4=CE=CD=C5=D6=CA115478 - 300 =E3=F0=ED=C4=EE=ED=E5=F6=EA=E0=FF =EE=E1=EB= =E0=F1=F2=FC197473 - 400 =E3=F0=ED =C6=C8=D2=CE=CC=C8=D086264 - 250 =E3=F0=ED=C6=E8=F2=EE=EC=E8=F0=F1=EA=E0=FF= =EE=E1=EB=E0=F1=F2=FC135276 - 350 =E3=F0=ED =C7=C0=CF=CE=D0=CE=C6=DC=C568395 - 200 =E3=F0=ED=C7=E0=EF=EE=F0=EE=E6=F1=EA= =E0=FF =EE=E1=EB=E0=F1=F2=FC97356 - 300 =E3=F0=ED =C8=C2=C0=CD=CE-=D4=D0=C0=CD=CA=CE=C2=D1=CA59367 - 200 =E3=F0=ED=C8=E2=E0= =ED=EE-=D4=F0=E0=ED=EA=EE=E2=F1=EA=E0=FF =EE=E1=EB=E0=F1=F2=FC86467 - 250= =E3=F0=ED =CA=C8=C5=C2 (=F4=E8=E7 =EB=E8=F6=E0)635286 - 550 =E3=F0=ED=CA=E8=E5=E2=F1= =EA=E0=FF =EE=E1=EB=E0=F1=F2=FC974164 - 650 =E3=F0=ED =CA=C8=C5=C2 (=EF=F0=E5=E4=EF=F0=E8=FF=F2=E8=FF)34286 - 200 =E3=F0=ED=CA=E8= =E5=E2=F1=EA=E0=FF =EE=E1=EB=E0=F1=F2=FC51639 - 300 =E3=F0=ED =CA=C8=D0=CE=C2=CE=C3=D0=C0=C456934 - 200 =E3=F0=ED=CA=E8=F0=EE=E2=EE=E3=F0= =E0=E4=F1=EA=E0=FF =EE=E1=EB=E0=F1=F2=FC79364 - 250 =E3=F0=ED =CB=D3=C3=C0=CD=D1=CA67385 - 250 =E3=F0=ED=CB=F3=E3=E0=ED=F1=EA=E0=FF =EE= =E1=EB=E0=F1=F2=FC91454 - 300 =E3=F0=ED =CB=D3=D6=CA48367 - 200 =E3=F0=ED=C2=EE=EB=FB=ED=F1=EA=E0=FF =EE=E1=EB=E0= =F1=F2=FC78539 - 250 =E3=F0=ED =CB=DC=C2=CE=C282629 - 250 =E3=F0=ED=CB=FC=E2=EE=E2=F1=EA=E0=FF =EE=E1=EB= =E0=F1=F2=FC126492 - 350 =E3=F0=ED =CD=C8=CA=CE=CB=C0=C5=C251537 - 250 =E3=F0=ED=CD=E8=EA=EE=EB=E0=E5=E2=F1=EA= =E0=FF =EE=E1=EB=E0=F1=F2=FC94175 - 300 =E3=F0=ED =CE=C4=C5=D1=D1=C0126385 - 350 =E3=F0=ED=CE=E4=E5=F1=F1=EA=E0=FF =EE=E1=EB= =E0=F1=F2=FC185473 - 400 =E3=F0=ED =CF=CE=CB=D2=C0=C2=C042856 - 200 =E3=F0=ED=CF=EE=EB=F2=E0=E2=F1=EA=E0=FF = =EE=E1=EB=E0=F1=F2=FC74275 - 250 =E3=F0=ED =D0=CE=C2=CD=CE75385 - 250 =E3=F0=ED=D0=EE=E2=E5=ED=F1=EA=E0=FF =EE=E1=EB= =E0=F1=F2=FC102658 - 300 =E3=F0=ED =D1=C5=C2=C0=D1=D2=CE=CF=CE=CB=DC54285 - 200 =E3=F0=ED=CA=F0=FB=EC97462 -= 300 =E3=F0=ED =D1=C8=CC=D4=C5=D0=CE=CF=CE=CB=DC45286 - 200 =E3=F0=ED=CA=F0=FB=EC97462 -= 300 =E3=F0=ED =D1=D3=CC=DB58356 - 200 =E3=F0=ED=D1=F3=EC=F1=EA=E0=FF =EE=E1=EB=E0=F1=F2= =FC89462 - 300 =E3=F0=ED =D2=C5=D0=CD=CE=CF=CE=CB=DC39271 - 200 =E3=F0=ED=D2=E5=F0=ED=EE=EF=EE=EB=FC= =F1=EA=E0=FF =EE=E1=EB=E0=F1=F2=FC69357 - 250 =E3=F0=ED =D3=C6=C3=CE=D0=CE=C447173 - 200 =E3=F0=ED=C7=E0=EA=E0=F0=EF=E0=F2=F1=EA=E0= =FF =EE=E1=EB=E0=F1=F2=FC72591 - 250 =E3=F0=ED =D5=C0=D0=DC=CA=CE=C2147286 - 350 =E3=F0=ED=D5=E0=F0=FC=EA=EE=E2=F1=EA=E0= =FF =EE=E1=EB=E0=F1=F2=FC205375 - 400 =E3=F0=ED =D5=C5=D0=D1=CE=CD97290 - 300 =E3=F0=ED=D5=E5=F0=F1=EE=ED=F1=EA=E0=FF =EE= =E1=EB=E0=F1=F2=FC121759 - 350 =E3=F0=ED =D5=CC=C5=CB=DC=CD=C8=D6=CA=C8=C984677 - 250 =E3=F0=ED=D5=EC=E5=EB=FC=ED=E8= =F6=EA=E0=FF =EE=E1=EB=E0=F1=F2=FC110475 - 300 =E3=F0=ED =D7=C5=D0=CA=C0=D1=D1=DB45289 - 200 =E3=F0=ED=D7=E5=F0=EA=E0=F1=F1=EA=E0=FF= =EE=E1=EB=E0=F1=F2=FC71492 - 250 =E3=F0=ED =D7=C5=D0=CD=C8=C3=CE=C268438 - 250 =E3=F0=ED=D7=E5=F0=ED=E8=E3=EE=E2=F1=EA= =E0=FF =EE=E1=EB=E0=F1=F2=FC84296 - 300 =E3=F0=ED =D7=C5=D0=CD=CE=C2=D6=DB44287 - 200 =E3=F0=ED=D7=E5=F0=ED=EE=E2=E8=F6=EA=E0= =FF =EE=E1=EB=E0=F1=F2=FC61731 - 250 =E3=F0=ED =D0=E0=F1=F1=FB=EB=EA=E0 =EF=EE =E2=F1=E5=E9 =E1=E0=E7=E5 =D3=EA=F0=E0=E8= =ED=FB =F1=F2=EE=E8=F2 13OO =E3=F0=ED. =CE=E1=F0=E0=F9=E0=E5=EC =C2=E0=F8=E5 =E2=ED=E8=EC=E0=ED=E8=E5 - =EC=E0=EA= =E5=F2=FB =F1=EE=E4=E5=F0=E6=E0=F9=E8=E5 =EF=EE=F0=ED=EE, =E0=E3=E8=F2=E8= =F0=F3=FE=F9=E8=E5 =EA =ED=E0=F1=E8=EB=E8=FE =E8 =EF=F0=EE=F2=E8=E2=EE=F0=E5=F7=E0=F9=E8=E5 =E4=E5=E9=F1=F2=E2=F3=FE=F9=E5= =EC=F3 =E7=E0=EA=EE=ED=EE=E4=E0=F2=E5=EB=FC=F1=F2=E2=F3 =D3=EA=F0=E0=E8=ED= =FB, =EA =F0=E0=F1=F1=FB=EB=EA=E5 =ED=E5 =EF=F0=E8=ED=E8=EC=E0=FE=F2=F1=FF= . =D2=E0=EA =E6=E5 =EF=F0=E5=E4=EB=E0=E3=E0=E5=EC =F0=E0=E7=EB=E8=F7=ED=FB=E5= =E1=E0=E7=FB =E4=E0=ED=ED=FB=F5 =E8 =F1=EF=F0=E0=E2=EE=F7=ED=E8=EA=E8, =EF= =F0=E0=E9=F1 =E2=FB=F1=FB=EB=E0=E5=EC =EF=EE =E7=E0=EF=F0=EE=F1=F3. =C2=CD=C8=CC=C0=CD=C8=C5! =CF=C8=D8=C8=D2=C5 =D2=CE=CB=DC=CA=CE =CD=C0 =D3= =CA=C0=C7=C0=CD=CD=DB=C9 =CD=C8=C6=C5 =C5=CC=C0=C8=CB =C0=C4=D0=C5=D1 =C8= =CB=C8 =C7=C2=CE=CD=C8=D2=C5 =CF=CE =D2=C5=CB=C5=D4=CE=CD=D3. =20 --- =D1 =F3=E2=E0=E6=E5=ED=E8=E5=EC =EE=F2=E4=E5=EB =F0=E5=EA=EB=E0=EC=FB =C2=EB=E0=E4=E8=EC=E8=F0 =C2=E8=EA=F2= =EE=F0=EE=E2=E8=F7 =F2=E5=EB: + 38063-637-4525 =F2=E5=F5=ED=E8=F7=E5=F1=EA=E8=E5 =E2=EE=EF=F0=EE=F1=FB =D1=E5=F0=E3=E5=E9= =C2=E0=EB=E5=F0=FC=E5=E2=E8=F7 =F2=E5=EB: + 38093-85599-27 mail: 932082@ukr.net skype: djinodjino74 icq: 653350891 =CE=D2=CF=C8=D1=C0=D2=DC=D1=DF =CE=D2 =D0=C0=D1=D1=DB=CB=CA=C8=CF=CE=C6= =C0=CB=CE=C2=C0=D2=DC=D1=DF =CD=C0 =D1=CF=C0=CC From owner-freebsd-ppc@freebsd.org Wed Mar 9 19:23:32 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8F982AC9D1C for ; Wed, 9 Mar 2016 19:23:32 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-4.reflexion.net [208.70.210.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3E0741A5B for ; Wed, 9 Mar 2016 19:23:31 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 12772 invoked from network); 9 Mar 2016 19:16:49 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 9 Mar 2016 19:16:49 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v7.80.0) with SMTP; Wed, 09 Mar 2016 14:16:55 -0500 (EST) Received: (qmail 8681 invoked from network); 9 Mar 2016 19:16:55 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with SMTP; 9 Mar 2016 19:16:55 -0000 X-No-Relay: not in my network X-No-Relay: not in my network X-No-Relay: not in my network Received: from [192.168.1.8] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id C25F91C43CC; Wed, 9 Mar 2016 11:16:47 -0800 (PST) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Ulrich Weigand has confirmed 3 of my 4 llvm bug submittals for clang 3.8.0 targeting powerpc/powerpc64. . . Date: Wed, 9 Mar 2016 11:16:50 -0800 Message-Id: Cc: Roman Divacky To: FreeBSD PowerPC ML , FreeBSD Toolchain Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.21 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 Mar 2016 19:23:32 -0000 [He also includes a note about ELFV2 ABI for powerpc64le.] Quoting llvm 26856 Comment 6 (he put the text in the 26856 submittal but = the content also covers 26519 and most of 26844): > Ulrich Weigand 2016-03-09 11:53:17 CST >=20 > Yes, there's indeed a couple of problems here, which affect different = areas. >=20 > 1) On 32-bit ppc, LLVM violates the ABI by storing below the stack = pointer even though the ABI does not provide a "red zone". This affects = every function with a stack frame, and could in theory lead to spurious = crashes when an asynchronous signal overwrites this area. This seems to = be a known issue; the source code contains FIXME lines: > // FIXME: On PPC32 SVR4, we must not spill before claiming the = stackframe. >=20 > 2) In some scenarios, registers may be spilled/restored twice to the = stack. This happens because while most of the spilling happens in = PPCFrameLowering::spillCalleeSavedRegisters, a few selected registers = are also spilled in PPCFrameLowering::emitPrologue. Those registers are = the frame pointer, base pointer, PIC base pointer, link register, and = condition code register. For the latter two, code ensures that they can = never be spilled in both places (for CR, there is extra code in = spillCalleeSavedRegisters; for LR, the register is removed from = SavedRegs in determineCalleeSaves). >=20 > However, for FP, BP, and PBP, nothing ensures the registers are not = spilled twice. It is probably *rare* for this to happen, because the = register allocator will not use those registers within the function if = they're needed for their special purpose, but it can happen in rare = cases. This includes the case of a system unwinder routine that uses = __builtin_unwind_init, but could also include other routines that = clobber one of those registers, e.g. the following case: >=20 > void func (void); >=20 > void test (void) > { > func (); > asm ("nop" : : : "31"); > } >=20 > When it happens that a register is spilled twice, the code as such = still works correctly, but the DWARF CFI unwind info associated with the = routine will be broken, which can mess up both C++ exception handling = and debugging. >=20 > 3) For the specific case of system unwinder routines that use = __builtin_unwind_init and/or __builtin_eh_return, special things need to = happen in the prolog and epilog that are not required for any other = routine. This in particular includes setting up save areas and CFI = records for the EH data registers (r3 ... r6). [See bug #26844. ] For = the ELFv2 ABI (powerpc64le), it also include using three separate save = areas for the three caller-saved condition register fields, so that the = EH logic can overwrite their values independently. >=20 > None of this is currently implemented in LLVM, since on Linux = generally GCC is used to build the system unwind libraries, and no other = code in the system ever needs those special constructs. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Wed Mar 9 20:24:08 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 553DDAC92B7 for ; Wed, 9 Mar 2016 20:24:08 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-5.reflexion.net [208.70.210.5]) (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 1B3721E94 for ; Wed, 9 Mar 2016 20:24:07 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 19242 invoked from network); 9 Mar 2016 20:24:06 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 9 Mar 2016 20:24:06 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v7.80.0) with SMTP; Wed, 09 Mar 2016 15:24:22 -0500 (EST) Received: (qmail 21535 invoked from network); 9 Mar 2016 20:24:21 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with SMTP; 9 Mar 2016 20:24:21 -0000 X-No-Relay: not in my network X-No-Relay: not in my network X-No-Relay: not in my network Received: from [192.168.1.8] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 848D21C43CC; Wed, 9 Mar 2016 12:24:01 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: Ulrich Weigand has confirmed 3 of my 4 llvm bug submittals for clang 3.8.0 targeting powerpc/powerpc64. . . From: Mark Millard In-Reply-To: Date: Wed, 9 Mar 2016 12:24:04 -0800 Cc: Roman Divacky Content-Transfer-Encoding: quoted-printable Message-Id: References: To: FreeBSD PowerPC ML , FreeBSD Toolchain X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.21 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 Mar 2016 20:24:08 -0000 On 2016-Mar-9, at 11:16 AM, Mark Millard wrote: >=20 > [He also includes a note about ELFV2 ABI for powerpc64le.] >=20 > Quoting llvm 26856 Comment 6 (he put the text in the 26856 submittal = but the content also covers 26519 and most of 26844): >=20 >> Ulrich Weigand 2016-03-09 11:53:17 CST >>=20 >> Yes, there's indeed a couple of problems here, which affect different = areas. >>=20 >> 1) On 32-bit ppc, LLVM violates the ABI by storing below the stack = pointer even though the ABI does not provide a "red zone". This affects = every function with a stack frame, and could in theory lead to spurious = crashes when an asynchronous signal overwrites this area. This seems to = be a known issue; the source code contains FIXME lines: >> // FIXME: On PPC32 SVR4, we must not spill before claiming the = stackframe. >>=20 >> 2) In some scenarios, registers may be spilled/restored twice to the = stack. This happens because while most of the spilling happens in = PPCFrameLowering::spillCalleeSavedRegisters, a few selected registers = are also spilled in PPCFrameLowering::emitPrologue. Those registers are = the frame pointer, base pointer, PIC base pointer, link register, and = condition code register. For the latter two, code ensures that they can = never be spilled in both places (for CR, there is extra code in = spillCalleeSavedRegisters; for LR, the register is removed from = SavedRegs in determineCalleeSaves). >>=20 >> However, for FP, BP, and PBP, nothing ensures the registers are not = spilled twice. It is probably *rare* for this to happen, because the = register allocator will not use those registers within the function if = they're needed for their special purpose, but it can happen in rare = cases. This includes the case of a system unwinder routine that uses = __builtin_unwind_init, but could also include other routines that = clobber one of those registers, e.g. the following case: >>=20 >> void func (void); >>=20 >> void test (void) >> { >> func (); >> asm ("nop" : : : "31"); >> } >>=20 >> When it happens that a register is spilled twice, the code as such = still works correctly, but the DWARF CFI unwind info associated with the = routine will be broken, which can mess up both C++ exception handling = and debugging. >>=20 >> 3) For the specific case of system unwinder routines that use = __builtin_unwind_init and/or __builtin_eh_return, special things need to = happen in the prolog and epilog that are not required for any other = routine. This in particular includes setting up save areas and CFI = records for the EH data registers (r3 ... r6). [See bug #26844. ] For = the ELFv2 ABI (powerpc64le), it also include using three separate save = areas for the three caller-saved condition register fields, so that the = EH logic can overwrite their values independently. >>=20 >> None of this is currently implemented in LLVM, since on Linux = generally GCC is used to build the system unwind libraries, and no other = code in the system ever needs those special constructs. >=20 >=20 > =3D=3D=3D > Mark Millard > markmi at dsl-only.net One point of his note is wrong: when the 2nd "spill" of a register is = after it had been changed it makes a bigger difference. I commented = back: > However, for FP, BP, and PBP, nothing ensures the registers are not = spilled > twice.. . . >=20 > When it happens that a register is spilled twice, the code as such = still > works correctly, but the DWARF CFI unwind info associated with the = routine > will be broken, which can mess up both C++ exception handling and = debugging. I will note that the Frame Pointer Register (r31) being saved again to = the same location but after it was adjusted to match the adjusted stack = pointer in the callee does not work correctly in that the restore of the = Frame Pointer for the return to the caller will restore the wrong = pointer value. If the caller then uses r31 without separately also restoring r31 first = then it will be addressing the wrong memory on the stack. The observed/reported code sequence had the 2nd r31 store in the callee = after r31 had been adjusted to match the adjusted stack pointer in the = callee. So more than C++ exception handling and debugging is broken for the = reported code sequence. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Fri Mar 11 09:36:31 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E4EDFACBE2F for ; Fri, 11 Mar 2016 09:36:31 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-5.reflexion.net [208.70.210.5]) (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 AAE9612BC for ; Fri, 11 Mar 2016 09:36:31 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 23732 invoked from network); 11 Mar 2016 09:36:22 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 11 Mar 2016 09:36:22 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v7.80.0) with SMTP; Fri, 11 Mar 2016 04:36:27 -0500 (EST) Received: (qmail 22309 invoked from network); 11 Mar 2016 09:36:27 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with SMTP; 11 Mar 2016 09:36:27 -0000 X-No-Relay: not in my network X-No-Relay: not in my network X-No-Relay: not in my network Received: from [192.168.1.8] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id A838C1C43CD; Fri, 11 Mar 2016 01:36:22 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: Ulrich Weigand has confirmed 3 of my 4 llvm bug submittals for clang 3.8.0 targeting powerpc/powerpc64. . . From: Mark Millard In-Reply-To: Date: Fri, 11 Mar 2016 01:36:22 -0800 Cc: Roman Divacky Content-Transfer-Encoding: quoted-printable Message-Id: <2ADD6542-E994-4FF9-B743-F6A03B1DCBCC@dsl-only.net> References: To: FreeBSD PowerPC ML , FreeBSD Toolchain X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.21 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 Mar 2016 09:36:32 -0000 [Some more details confirmed.] On 2016-Mar-9, at 12:24 PM, Mark Millard wrote: >=20 > On 2016-Mar-9, at 11:16 AM, Mark Millard = wrote: >>=20 >> [He also includes a note about ELFV2 ABI for powerpc64le.] >>=20 >> Quoting llvm 26856 Comment 6 (he put the text in the 26856 submittal = but the content also covers 26519 and most of 26844): >>=20 >>> Ulrich Weigand 2016-03-09 11:53:17 CST >>>=20 >>> Yes, there's indeed a couple of problems here, which affect = different areas. >>>=20 >>> 1) On 32-bit ppc, LLVM violates the ABI by storing below the stack = pointer even though the ABI does not provide a "red zone". This affects = every function with a stack frame, and could in theory lead to spurious = crashes when an asynchronous signal overwrites this area. This seems to = be a known issue; the source code contains FIXME lines: >>> // FIXME: On PPC32 SVR4, we must not spill before claiming the = stackframe. >>>=20 >>> 2) In some scenarios, registers may be spilled/restored twice to the = stack. This happens because while most of the spilling happens in = PPCFrameLowering::spillCalleeSavedRegisters, a few selected registers = are also spilled in PPCFrameLowering::emitPrologue. Those registers are = the frame pointer, base pointer, PIC base pointer, link register, and = condition code register. For the latter two, code ensures that they can = never be spilled in both places (for CR, there is extra code in = spillCalleeSavedRegisters; for LR, the register is removed from = SavedRegs in determineCalleeSaves). >>>=20 >>> However, for FP, BP, and PBP, nothing ensures the registers are not = spilled twice. It is probably *rare* for this to happen, because the = register allocator will not use those registers within the function if = they're needed for their special purpose, but it can happen in rare = cases. This includes the case of a system unwinder routine that uses = __builtin_unwind_init, but could also include other routines that = clobber one of those registers, e.g. the following case: >>>=20 >>> void func (void); >>>=20 >>> void test (void) >>> { >>> func (); >>> asm ("nop" : : : "31"); >>> } >>>=20 >>> When it happens that a register is spilled twice, the code as such = still works correctly, but the DWARF CFI unwind info associated with the = routine will be broken, which can mess up both C++ exception handling = and debugging. >>>=20 >>> 3) For the specific case of system unwinder routines that use = __builtin_unwind_init and/or __builtin_eh_return, special things need to = happen in the prolog and epilog that are not required for any other = routine. This in particular includes setting up save areas and CFI = records for the EH data registers (r3 ... r6). [See bug #26844. ] For = the ELFv2 ABI (powerpc64le), it also include using three separate save = areas for the three caller-saved condition register fields, so that the = EH logic can overwrite their values independently. >>>=20 >>> None of this is currently implemented in LLVM, since on Linux = generally GCC is used to build the system unwind libraries, and no other = code in the system ever needs those special constructs. >>=20 >>=20 >> =3D=3D=3D >> Mark Millard >> markmi at dsl-only.net >=20 > One point of his note is wrong: when the 2nd "spill" of a register is = after it had been changed it makes a bigger difference. I commented = back: >=20 >=20 >> However, for FP, BP, and PBP, nothing ensures the registers are not = spilled >> twice.. . . >>=20 >> When it happens that a register is spilled twice, the code as such = still >> works correctly, but the DWARF CFI unwind info associated with the = routine >> will be broken, which can mess up both C++ exception handling and = debugging. >=20 >=20 > I will note that the Frame Pointer Register (r31) being saved again to = the same location but after it was adjusted to match the adjusted stack = pointer in the callee does not work correctly in that the restore of the = Frame Pointer for the return to the caller will restore the wrong = pointer value. >=20 > If the caller then uses r31 without separately also restoring r31 = first then it will be addressing the wrong memory on the stack. >=20 > The observed/reported code sequence had the 2nd r31 store in the = callee after r31 had been adjusted to match the adjusted stack pointer = in the callee. >=20 > So more than C++ exception handling and debugging is broken for the = reported code sequence. The new comments are. . . > Comment # 9 on bug 26856 from Ulrich Weigand > (In reply to comment #8) >=20 > > (In reply to comment #6 > ) > >=20 > > > However, for FP, BP, and PBP, nothing ensures the registers are = not spilled > > > twice.. . . > > >=20 > > > When it happens that a register is spilled twice, the code as such = still > > > works correctly, but the DWARF CFI unwind info associated with the = routine > > > will be broken, which can mess up both C++ exception handling and = debugging. > >=20 > > I will note that the Frame Pointer Register (r31) being saved again = to the > > same location but after it was adjusted to match the adjusted stack = pointer > > in the callee does not work correctly in that the restore of the = Frame > > Pointer for the return to the caller will restore the wrong pointer = value. > >=20 > > If the caller then uses r31 without separately also restoring r31 = first then > > it will be addressing the wrong memory on the stack. > >=20 > > The observed/reported code sequence had the 2nd r31 store in the = callee > > after r31 had been adjusted to match the adjusted stack pointer in = the > > callee. > >=20 > > So more than C++ exception handling and debugging is broken for the = reported > > code sequence. >=20 >=20 > Ah, right. I had been under the impression that the back-end would = use two > different save areas, but indeed it does use the same area, just = addressed > slightly differently. The resulting code is then just simply = incorrect. and. . . > Comment # 10 on bug 26856 from Ulrich Weigand > (In reply to comment #7) >=20 >=20 > > The observed behavior for the powerpc (what should be) SVR4 context = is that > > the save/restore logic for CR fields 2, 3, 4 is present but no = .eh_frame > > information is written out for the EH logic to use for CR. >=20 >=20 > Huh, indeed. This is yet another bug, which also affects functions = for the > powerpc (SVR4) ABI in general, not just unwind system routines. >=20 > This seems to be a logic issue here: >=20 > // For SVR4, don't emit a move for the CR spill slot if we = haven't > // spilled CRs. > if (isSVR4ABI && (PPC::CR2 <=3D Reg && Reg <=3D PPC::CR4) > && !MustSaveCR) > continue; >=20 > MustSaveCR is always false for 32-bit, it is only used on 64-bit. = This has the > effect that on 32-bit, we never get any CFI for the CRs. =3D=3D=3D Mark Millard markmi at dsl-only.net