From owner-freebsd-ppc@freebsd.org Mon Mar 13 01:53:36 2017 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 76950D08C43 for ; Mon, 13 Mar 2017 01:53:36 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-211-181.reflexion.net [208.70.211.181]) (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 26B8C1AE7 for ; Mon, 13 Mar 2017 01:53:35 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 18826 invoked from network); 13 Mar 2017 01:53:28 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 13 Mar 2017 01:53:28 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.30.2) with SMTP; Sun, 12 Mar 2017 21:53:28 -0400 (EDT) Received: (qmail 8024 invoked from network); 13 Mar 2017 01:53:27 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 13 Mar 2017 01:53:27 -0000 Received: from [192.168.1.111] (c-67-170-167-181.hsd1.or.comcast.net [67.170.167.181]) by iron2.pdx.net (Postfix) with ESMTPSA id 1A347EC8662; Sun, 12 Mar 2017 18:53:27 -0700 (PDT) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example) Message-Id: <3EDEF0B7-59C5-4648-9737-6682E18645BC@dsl-only.net> Date: Sun, 12 Mar 2017 18:53:26 -0700 Cc: FreeBSD Toolchain , FreeBSD Current To: FreeBSD Ports , FreeBSD PowerPC ML X-Mailer: Apple Mail (2.3259) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Mar 2017 01:53:36 -0000 Summary: RAM+(peak swap) was about 26 GiBytes. Also: about 118 GiByte /usr/obj/. . ./llvm40/ area. (2 processors, 2 cores each, all in use; WITH_DEBUG=3D used) The peak usage times were when the 4 cores were each busy running ld at the same time. [So far as I know FreeBSD does not report peak swap usage "since boot". So I do not have a cross check on if I missed seeing a higher peak then I report in the details below.] What all this note spans as part of the build: # more /var/db/ports/devel_llvm40/options # This file is auto-generated by 'make config'. # Options for llvm40-4.0.0.r4 _OPTIONS_READ=3Dllvm40-4.0.0.r4 _FILE_COMPLETE_OPTIONS_LIST=3DCLANG DOCS EXTRAS LIT LLD LLDB OPTIONS_FILE_SET+=3DCLANG OPTIONS_FILE_SET+=3DDOCS OPTIONS_FILE_SET+=3DEXTRAS OPTIONS_FILE_SET+=3DLIT OPTIONS_FILE_SET+=3DLLD OPTIONS_FILE_SET+=3DLLDB The system clang 4.0 was used to do the build. A port binutils was used (-B${LOCALBASE}/bin/ in CFLAGS, CXXFLAGS, an CPPFLAGS). The kernel was non-debug generally but buildworld buildkernel did not have MALLOC_PRODUCTION=3D . The llvm40 build did have MALLOC_PRODUCTION=3D . # uname -paKU FreeBSD FBSDG5L 12.0-CURRENT FreeBSD 12.0-CURRENT r314687M powerpc = powerpc64 1200023 1200023 Most of what I have access to for FreeBSD does not have a big enough configuration to do a WITH_DEBUG=3D build of llvm40 on a machine with 4 cores, all in use. One type of environment that does is an old PowerMac G5 so-called "Quad Core" that has 16 GiBytes of RAM, 17 GiBytes of swap, and a 480 GiByte SSD (but extra over provisioned so it appears even smaller for the file system+swap). Watching with top the peak swap usage that I saw was 56% of the 17 GiByte --so call it 10 GiBytes or so. So something like 16 GiBytes RAM + 10 GiBytes swap and so something like 26 GiByte total. I used portmaster with -DK. Afterwards the /usr/obj/ sub-area for llvm40 used totaled to a size of: # du -sg /usr/obj/portswork/usr/ports/devel/llvm40 118 /usr/obj/portswork/usr/ports/devel/llvm40 So around 118 GiBytes of disk space. Showing the major space usage contributions: # du -sg /usr/obj/portswork/usr/ports/devel/llvm40/work/.build/* = /usr/obj/portswork/usr/ports/devel/llvm40/work/stage/usr/local/llvm40/* . . . 29 /usr/obj/portswork/usr/ports/devel/llvm40/work/.build/bin . . . 29 /usr/obj/portswork/usr/ports/devel/llvm40/work/.build/lib . . . 12 /usr/obj/portswork/usr/ports/devel/llvm40/work/.build/tools . . . 26 = /usr/obj/portswork/usr/ports/devel/llvm40/work/stage/usr/local/llvm40/bin . . . 24 = /usr/obj/portswork/usr/ports/devel/llvm40/work/stage/usr/local/llvm40/lib . . . Side notes that are more system specific: The timestamps on the script output file indicate that the build took about 8 hours 24 minutes. The powerpc64 system used was built with the system clang 4.0 compiler and a port-based binutils. This is despite that clang 4.0 produces code that has any thrown C++ exceptions completely non-functional for powerpc64 (program crashes via signals reporting problems). =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Mon Mar 13 16:55:20 2017 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 76D97D0A846 for ; Mon, 13 Mar 2017 16:55:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (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 3D45F1E20 for ; Mon, 13 Mar 2017 16:55:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by freefall.freebsd.org (Postfix) id 811A66BB3; Mon, 13 Mar 2017 16:55:19 +0000 (UTC) Delivered-To: freebsd-powerpc@localmail.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::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 6BE456BB2 for ; Mon, 13 Mar 2017 16:55:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 213EA1E19 for ; Mon, 13 Mar 2017 16:55:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v2DGtH7r027963 for ; Mon, 13 Mar 2017 16:55:18 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-powerpc@FreeBSD.org Subject: [Bug 217762] devel/qt5-qmake cannot be built on powerpc64 Date: Mon, 13 Mar 2017 16:55:17 +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: hiroo.ono+freebsd@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: kde@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter cc flagtypes.name attachments.created 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.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Mar 2017 16:55:20 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217762 Bug ID: 217762 Summary: devel/qt5-qmake cannot be built on powerpc64 Product: Ports & Packages Version: Latest Hardware: powerpc OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: kde@FreeBSD.org Reporter: hiroo.ono+freebsd@gmail.com CC: freebsd-powerpc@FreeBSD.org Flags: maintainer-feedback?(kde@FreeBSD.org) CC: freebsd-powerpc@FreeBSD.org Assignee: kde@FreeBSD.org Created attachment 180783 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D180783&action= =3Dedit failed build log from poudriere. as there is USES=3D compiler:c++11-lib in Makefile, CXX=3D"g++49" is specif= ied on MAKE_ENV section, but at the build phase, "g++" is used as the command. On powerpc64, it triggers gcc 4.2.1 in base, which does not support c++11. poudriere log on FreeBSD/powerpc64 r313561 attached. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-ppc@freebsd.org Thu Mar 16 16:05:13 2017 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 E8D86D0F361 for ; Thu, 16 Mar 2017 16:05:13 +0000 (UTC) (envelope-from david.smith@cioutlookreports.com) Received: from mailer57.gate93.rs.smtp.com (mailer57.gate93.rs.smtp.com [74.91.93.57]) (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 A955E161B for ; Thu, 16 Mar 2017 16:05:13 +0000 (UTC) (envelope-from david.smith@cioutlookreports.com) X-MSFBL: fW5IxAHOrGDcLRJAdVQjwGJ8mLG1Q5TtlyHl8viaKuk=|eyJnIjoiQ29tbW9kaXR 5SW5zaWRlX2RlZGljYXRlZF9wb29sIiwiYiI6Ijc0XzkxXzkzXzU3IiwiciI6ImZ yZWVic2QtcHBjQGZyZWVic2Qub3JnIn0= Received: from [192.168.80.32] ([192.168.80.32:53860] helo=rs-ord-mta03-in2.smtp.com) by rs-ord-mta02-out1.smtp.com (envelope-from ) (ecelerity 4.2.1.55028 r(Core:4.2.1.12)) with ESMTP id 0E/81-09022-103BAC85; Thu, 16 Mar 2017 15:45:05 +0000 DKIM-Signature: v=1; a=rsa-sha256; d=smtp.com; s=smtpcomcustomers; c=relaxed/simple; q=dns/txt; i=@smtp.com; t=1489679105; h=From:Subject:To:Date:MIME-Version:Content-Type; bh=odRDJzCmSRxLk6wFcAHjVLh9Qj8yQmeYFaHCwijPeRM=; b=baQXZspsr4abCoFYHPKTRc7C8LRfwYjHm6Q8IALJ4FUa7E5Tu8CR2pCoGIjgZDY9 zZ20dp86r4ekNJUoOuIrWxnjCIRhgyg110xufGBe0Ri4jcpP3YC+ElXp2+C9llNz Y29Bjh0Bw99oH8nSjnKELxQ2jXM44h+nLEojyy/O070=; Received: from [86.4.116.225] ([86.4.116.225:36032] helo=cpc90280-cove16-2-0-cust224.3-1.cable.virginm.net) by rs-ord-mta03-in2.smtp.com (envelope-from ) (ecelerity 4.1.0.46749 r(Core:4.1.0.4)) with ESMTPA id 62/00-18959-103BAC85; Thu, 16 Mar 2017 15:45:05 +0000 MIME-Version: 1.0 From: "David Smith" Reply-To: david.smith@cioutlookreports.com To: freebsd-ppc@freebsd.org Subject: Global Vehicle-to-Everything (V2X) Communications Market out to 2027 X-Mailer: Smart_Send_2_0_138 Date: Thu, 16 Mar 2017 15:45:01 +0000 Message-ID: <22563930369282563212677@Saket> 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. X-SMTPCOM-Tracking-Number: c073126d-17a3-4226-b416-7a36fd8ce7b5 X-SMTPCOM-Sender-ID: 5012537 Feedback-ID: 5012537:SMTPCOM Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Mar 2017 16:05:14 -0000 Global Vehicle-to-Everything (V2X) Communications Market out to 2027 (Repor= t) =20 Report Information: Release Date: March 2017 Number of Pages/Slides: 103 Tables and Figures: 67 Report Overview: =20 The global vehicle-to-everything (V2X) communications market is expected to= see significant growth over the next ten years. Some of the major drivers = behind the growth will be stringent safety regulations, increased demand fo= r connectivity and development of autonomous vehicles. Meanwhile, growth wi= ll shift from North America and Western Europe to Asia, especially China. The V2X market has evolved through a raft of regulations, and government an= d private investments. It will see further legislations and renewed market = growth on the back of rapid adoption of V2V and V2I communication technolog= ies. Commodity Inside understands that demand for automotive connectivity is at = its embryonic stage and has an enormous growth potential. V2X communication= technologies will enhance existing safety features and help developing new= applications. With automakers planning to introduce fully autonomous vehic= les by 2021, V2X will be one of the major beneficiaries and will see a surg= e in sales. The deployment of 5G cellular technology will also put pressure on the exis= ting dedicated short-range communications (DSRC) technology. However, both = technologies would have limitations, so both will continue to be used over = the next ten years. The 5G technology will open new opportunities for big d= ata and big data analytics, allowing the fastest transmission of the vast a= mount of live data. The expected high growth and rising adoption have also opened new opportuni= ties for high-tech companies. Vehicles are increasingly becoming vulnerable= to hacking as they are interacting with others vehicles and devices. Conse= quently, this has opened new venues for cyber security companies which are = penetrating quite rapidly in the automotive market. Why this report is unique and a must read for the V2X and automotive indust= ry as a whole=3F Global Vehicle-to-Everything (V2X) Communications Market out to 2027 is a v= aluable resource necessary for examining the global V2X communications mark= et. We have employed a very sophisticated and robust approach to assess the= automotive market by taking into account various demand and supply dynamic= s as well as technological developments. The report has also encompassed di= fferent segmentations of the market and strategic directions for OEMs and T= ier-1 suppliers going forward. The report covers the following key aspects: How will the V2X market perform over the next ten-years=3F What will be the major factors driving the V2X communications market and ho= w they will impact the industry=3F How will the increasing use of communications technology benefit the indust= ry=3F Detailed analysis of the current status of V2X communications supply chain=3F What will be the major drivers behind each type of communication, connectiv= ity, applications, hardware & software and vehicle type and what will be th= eir implications=3F Analysis and ten year projections for V2V, V2I, V2P, V2G and V2N markets. The current and future demand dynamics of OEMs and aftermarket in the V2V c= ommunications segment. Projections of the roadside equipment installation in the V2I market. Detailed discussion on market strategies and competitive landscapes. Analysis of the present and future performance of matured and developing ma= rkets. Why should you read this report=3F Global Vehicle-to-Everything (V2X) Communications Market out to 2027 provid= es you with the following in-depth analysis: The V2X communications market is analysed by five communications segments, = by vehicle type, by connectivity type, by applications and by hardware & so= ftware. Discussion on major drivers and restraints of each communications segment. The full coverage of V2X communications market in terms of sales value. Coverage of the whole world by five regions and ten selected major countrie= s. Detailed analysis of the current and future supply chain. Market projections for roadside units installation and OEM-aftermarket dyna= mics in the V2V segment. 67 tables, figures and charts. All supportive data provided in Excel. Who should buy this report=3F Conventional car manufacturers Electric vehicle manufacturers Hybrid and plug-in hybrid vehicles manufacturers Component manufacturers Suppliers of materials to automotive Automotive technology vendors Software and cyber security companies Mobile network operators Smartphone manufacturers Mobility service providers Utility companies Financial institutions Industry consultants, researchers and analysts Government bodies Why our analyses are robust and authoritative=3F We constantly consult industry experts and incorporate their views in our a= nalysis.=20 We employ both quantitative and qualitative methods to derive robust analys= is.=20 All our forecast data were also supported by our proprietary econometric an= d excel based models.=20 We are completely independent and represent our own views. =20 Table of Contents Chapter 1- Executive Summary 1.1 Developments in the V2X communications market Chapter 2 =96 Introduction and Methodology 2.1 Introduction 2.2 Methodology Chapter 3 =96 V2X Market Segmentations 3.1 V2X market by communication 3.1.1 Vehicle-to-Vehicle (V2V) 3.1.2 Vehicle-to-Infrastructure (V2I) 3.1.3 Vehicle-to-Pedestrian (V2P) 3.1.4 Vehicle-to-Grid (V2G) 3.1.5 Vehicle-to-Network (V2N) 3.2 V2X market by vehicle type 3.3 V2X market by connectivity type 3.4 V2X market by offering 3.5 V2X market by application type Chapter 4 =96 V2X Market by Geography 4.1 Brazil 4.2 Canada 4.3 China 4.4 France 4.5 Germany 4.6 India 4.7 Japan 4.8 South Korea 4.9 UK 4.10 US Chapter 5 =96 Competitive Landscape 5.1 Competitive landscape by major partnerships and M&As 5.3 Company profiles by OEMS and Teir-1 suppliers List of Tables: Table 1.1 Global V2X market by region 2014-2027 ($ billions) Table 1.2 Global V2X market by communication segments 2014-2027 ($ millions) Table 3.1 Global V2V market 2014-2027 ($ millions) Table 3.2 Global OEM and Aftermarket V2V market 2014-2027 ($ millions) Table 3.3 Global V2I market 2014-2027 ($ millions, %) Table 3.4 Global roadside units installations 2014-2027 (=91000 units) Table 3.5 Global V2P market 2014-2027 ($ millions, %) Table 3.6 Global V2P enabled smartphone shipments 2014-2027 (million units) Table 3.7 Global V2G market 2014-2027 ($ millions, %) Table 3.8 Global V2N market 2014-2027 ($ million, %) Table 3.9 Global V2X market by offerings 2014-2027 ($ millions) Table 4.1 Brazilian V2X market 2014-2027 ($ millions, %) Table 4.2 Canadian V2X market 2014-2027 ($ millions, %) Table 4.3 Chinese V2X market 2014-2027 ($ millions, %) Table 4.4 French V2X market 2014-2027 ($ millions, %) Table 4.5 German V2X market 2014-2027 ($ millions, %) Table 4.6 Indian V2X market 2014-2027 ($ millions, %) Table 4.7 Japanese V2X market 2014-2027 ($ millions, %) Table 4.8 South Korean V2X market 2014-2027 ($ millions, %) Table 4.9 UK V2X market 2014-2027 ($ millions, %) Table 4.10 US V2X market 2014-2027 ($ millions, %) =20 List of Figures: Figure 1.1 Global V2X market by region 2014-2027 ($ billions) Figure 1.2 Global V2X market by segment 2014-2027 ($ millions) Figure 1.3 Global V2X market by application 2014-2027 ($ billions) Figure 1.4 Global V2X market by type of vehicle 2014-2027 ($ billions) Figure 1.5 Global V2X market by connectivity 2014-2027 ($ billions) Figure 1.6 Global V2X market by offering 2014-2027 ($ billions) Figure 3.1 Global V2V market 2014-2027 ($ millions) Figure 3.2 Global OEM and aftermarket V2X market 2014-2027 ($ millions) Figure 3.3 Global V2I market 2014-2027 ($ millions) Figure 3.4 Global roadside units installations 2014-2027 (=91000 units) Figure 3.5 Global V2P market ($ millions) Figure 3.6 Global V2P enabled device shipments 2014-2017 (million units) Figure 3.7 Global V2G market 2014-2027 ($ millions) Figure 3.8 Global V2N market 2014-2027 ($ billions) Figure 3.9 Global vehicle sales 2014-2027 (million units) Figure 3.10 Global light vehicles sales 2014-2027 (million units) Figure 3.11 Global medium and high vehicle sales 2014-2027 (million units) Figure 3.12 Global V2X light vehicles market 2014-2027 ($ billions) Figure 3.13 Global V2X medium and light vehicle market 2014-2027 ($ billion= s) Figure 3.14 Global V2X market 2014-2027 ($ billions) Figure 3.15 Global DSRC market 2014-2027 ($ billions) Figure 3.16 Global Cellular market 2014-2027 ($ billions) Figure 3.17 Global V2X market by offerings 2014-2027 ($ billions) Figure 3.18 Global V2X market by application ($ billions) Figure 3.19 Global V2X market share by application (% share) Figure 4.1 Brazilian V2X market 2014-2027 ($ millions) Figure 4.2 Canadian V2X market ($ millions) Figure 4.3 Chinese V2X market 2014-2027 ($ millions) Figure 4.4 French V2X market 2014-2027 ($ millions) Figure 4.5 German V2X market 2014-2027 ($ millions) Figure 4.6 Indian V2X market 2014-2027 ($ millions) Figure 4.7 Japanese V2X market 2014-2027 ($ millions) Figure 4.8 South Korean V2X market 2014-2027 ($ millions) Figure 4.9 UK V2X market 2014-2027 ($ million, %) Figure 4.10 US V2X market 2014-2027 ($ millions) =20 List of charts: Chart 1.1 Opportunities, challenges, readiness, regulations impact, time to= scale production and aftermarket potential in the V2X market by supply cha= in Chart 2.1 V2X market segments by communication type Chart 2.2 V2X communications process Chart 3.1 Comparison of DSRC and cellular applications Chart 3.2 Vehicle sensors by ADAS applications Chart 3.3 V2X application grouped by agency data, safety, mobility and road= weather Chart 4.1 Existing and future V2X applications in Japan Chart 5.1 List of vehicles with V2V and V2I capabilities by major OEMs Chart 5.2 List of major Tier-1 suppliers and their V2X portfolio Chart 5.3 Major partnerships in the V2X market 2015-2017 Chart 5.4 Mergers and acquisitions in the V2X market 2015-2017 =20 Report Pricing Single User License: =A31695 Departmental License (up to 5 Users): =A32995 Global License: =A34995 =20 Ordering process Please contact David Smith on david.smith@cioutlookreports.com And provide the following information: Report Title - Report License - (Single User/Departmental/Global) Name - Email - Job Title - Company - Invoice Address VAT number (EU Only) Please contact me if you have any questions, or wish to purchase a copy I look forward to hearing from you. Kind Regards David Smith Business Intelligence Executive To Unsubscribe send an email with Unsubscribe in the subject line to info@c= s-reports.com Remove From owner-freebsd-ppc@freebsd.org Sat Mar 18 20:12:33 2017 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 34249D1201C for ; Sat, 18 Mar 2017 20:12:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1B5221045 for ; Sat, 18 Mar 2017 20:12:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v2IKCWBr064908 for ; Sat, 18 Mar 2017 20:12:32 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ppc@FreeBSD.org Subject: [Bug 178038] clang++ fails to produce a binary in powerpc64 Date: Sat, 18 Mar 2017 20:12:33 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: powerpc X-Bugzilla-Version: 9.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: jhibbits@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Feedback Timeout X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-ppc@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status 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.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Mar 2017 20:12:33 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D178038 Justin Hibbits changed: What |Removed |Added ---------------------------------------------------------------------------- Status|In Progress |Closed Resolution|--- |Feedback Timeout --- Comment #2 from Justin Hibbits --- It's been 2 years since the last request for update. I've built many binar= ies on FreeBSD head with clang since then, but have not tried to reproduce the = test conditions. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-ppc@freebsd.org Sat Mar 18 22:11:15 2017 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 C7F9AD102EF for ; Sat, 18 Mar 2017 22:11:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9D6A21659 for ; Sat, 18 Mar 2017 22:11:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v2IMBFkB055574 for ; Sat, 18 Mar 2017 22:11:15 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ppc@FreeBSD.org Subject: [Bug 178038] clang++ fails to produce a binary in powerpc64 Date: Sat, 18 Mar 2017 22:11:15 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: powerpc X-Bugzilla-Version: 9.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: markmi@dsl-only.net X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Feedback Timeout X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-ppc@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Mar 2017 22:11:15 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D178038 Mark Millard changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |markmi@dsl-only.net --- Comment #3 from Mark Millard --- [This is not an objection to closing 178038. It is more of a status note since while kyua builds it does not work.] I've built kyua via system clang 3.8 and later for powerpc family members. The builds completed. But even as of clang 4.0 the code generation is bad and kyua fails to run. This is for both TARGET_ARCH=3Dpowerpc64 and TARGET_ARCH=3Dpowerpc. All of the below applies to clang 4.0 (so far). kyua makes extensive use of C++ exception handling, among other things. One problem for both TARGET_ARCH's is that handling thrown C++ exceptions is messed up. Even: #include int main(void) { try { throw std::exception(); } catch (std::exception& e) {} return 0; } fails. This makes kyua currently useless. TARGET_ARCH=3Dpowerpc also has problems with use and restore of R31 when floating point code is involved (restored for returning but later used for floating point code expecting R31 to not have been restored yet). (There may be more issues for one or both TARGET_ARCH's but the above is sufficient to classify clang as broken for kyua.) --=20 You are receiving this mail because: You are the assignee for the bug.=