From owner-freebsd-ppc@freebsd.org Tue May 2 08:37:28 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 A4115D5A87F for ; Tue, 2 May 2017 08:37:28 +0000 (UTC) (envelope-from andy.silva@snsmarketreports.com) Received: from mailer238.gate85.rs.smtp.com (mailer238.gate85.rs.smtp.com [74.91.85.238]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5744ADAC for ; Tue, 2 May 2017 08:37:28 +0000 (UTC) (envelope-from andy.silva@snsmarketreports.com) X-MSFBL: ZuBM1Iqt3HEQiOeE3wSOusAIjBRcfH73ePoVs5+c96E=|eyJiIjoiNzRfOTFfODV fMjM4IiwiciI6ImZyZWVic2QtcHBjQGZyZWVic2Qub3JnIiwiZyI6IlNuc3RlbGV jb21fZGVkaWNhdGVkX3Bvb2wifQ== Received: from [192.168.80.12] ([192.168.80.12:58586] helo=rs-ord-mta01-in2.smtp.com) by rs-ord-mta01-out2.smtp.com (envelope-from ) (ecelerity 4.2.1.55028 r(Core:4.2.1.12)) with ESMTP id 80/DC-04808-52738095; Tue, 02 May 2017 07:37:09 +0000 DKIM-Signature: v=1; a=rsa-sha256; d=snsresearchreports.com; s=snskey; c=relaxed/simple; q=dns/txt; i=@snsresearchreports.com; t=1493710629; h=From:Subject:To:Date:MIME-Version:Content-Type; bh=LYTt8d0jqKLMg71ffMorAmex4uAtuih4AFBxAI1Cm04=; b=mv1VQ0rHgQivwX4dDpPwdYFXG40hBY+5qdIYFQyuqEfGRtaetDyq8gQk2Gqcl6HY uoHVa+x36aBwHUV3hYYofaaPN6R/1Egl673N4KbjqaRrjT5/hJWPLASS6YT96l8x 6HTPKxiLYKxbnM5kzMm0gbjCgw0IqwrMvVCQLa76HQI1m/JmLbEzT49jkNEPD5+o RRYRVREQrmUBn510icEqq1W0IJEaAfKHmeTCzK20uoAiwBiuzFcwHDtb89W7VIa5 sgGLkle+TyQSNDsGXul/BNs75C9hPPKjAR3L6KZmTay/mhmsvdm/K3pyup9bVkVv LS5bKuEbpjWWN8CzCmDvoQ==; Received: from [24.84.197.89] ([24.84.197.89:32822] helo=S01061c1b689e28c7.vc.shawcable.net) by rs-ord-mta01-in2.smtp.com (envelope-from ) (ecelerity 4.1.0.46749 r(Core:4.1.0.4)) with ESMTPA id FB/08-21862-52738095; Tue, 02 May 2017 07:37:09 +0000 MIME-Version: 1.0 From: "Andy Silva" Reply-To: andy.silva@snsmarketreports.com To: freebsd-ppc@freebsd.org Subject: The Big Data Market: 2017 - 2030 - Opportunities, Challenges, Strategies, Industry Verticals & Forecasts (Report) X-Mailer: Smart_Send_2_0_138 Date: Tue, 2 May 2017 00:37:07 -0700 Message-ID: <2164405115656316561775@Ankur> 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: 5ea8a7d9-cb02-4ee7-b896-7f8469831702 X-SMTPCOM-Sender-ID: 6008902 Feedback-ID: 6008902:SMTPCOM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.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: Tue, 02 May 2017 08:37:28 -0000 The Big Data Market: 2017 =96 2030 =96 Opportunities, Challenges, Strategie= s, Industry Verticals & Forecasts (Report) Hello Please find the latest SNS Research report summary to you and your team, " = The Big Data Market: 2017 =96 2030 =96 Opportunities, Challenges, Strategie= s, Industry Verticals & Forecasts" Below is the report highlight and if you= like I can send you sample pages for your details inside. =20 Our reports are compiled with primary and secondary informations to produce= an overall industry outlook. Despite challenges relating to privacy concer= ns and organizational resistance, Big Data investments continue to gain mom= entum throughout the globe. SNS Research estimates that Big Data investment= s will account for over $57 Billion in 2017 alone. These investments are fu= rther expected to grow at a CAGR of approximately 10% over the next three y= ears. Report Information: Release Date: April 2017 Number of Pages: 498 Number of Tables and Figures: 89 Key Questions Answered: How big is the Big Data ecosystem=3F How is the ecosystem evolving by segment and region=3F What will the market size be in 2020 and at what rate will it grow=3F What trends, challenges and barriers are influencing its growth=3F Who are the key Big Data software, hardware and services vendors and what a= re their strategies=3F How much are vertical enterprises investing in Big Data=3F What opportunities exist for Big Data analytics=3F Which countries and verticals will see the highest percentage of Big Data i= nvestments=3F Key Findings: The report has the following key findings: In 2017, Big Data vendors will pocket over $57 Billion from hardware, softw= are and professional services revenues. These investments are further expec= ted to grow at a CAGR of approximately 10% over the next four years, eventu= ally accounting for over $76 Billion by the end of 2020. As part of wider plans to revitalize their economies, countries across the = world are incorporating legislative initiatives to capitalize on Big Data. = For example, the Japanese government is engaged in developing intellectual = property protection and dispute resolution frameworks for Big Data assets, = in a bid to encourage data sharing and accelerate the development of domest= ic industries. By the end of 2017, SNS Research estimates that as much as 30% of all Big D= ata workloads will be processed via cloud services as enterprises seek to a= void large-scale infrastructure investments and security issues associated = with on-premise implementations. The vendor arena is continuing to consolidate with several prominent M&A de= als such as computer hardware giant Dell's $60 Billion merger with data sto= rage specialist EMC. The report covers the following topics: Big Data ecosystem Market drivers and barriers Big Data technology, standardization and regulatory initiatives Big Data industry roadmap and value chain Analysis and use cases for 14 vertical markets Big Data analytics technology and case studies Big Data vendor market share Company profiles and strategies of over 240 Big Data ecosystem players Strategic recommendations for Big Data hardware, software and professional = services vendors, and enterprises Market analysis and forecasts from 2017 till 2030 Forecast Segmentation: Market forecasts and historical figures are provided for each of the follow= ing submarkets and their categories: Hardware, Software & Professional Services=20 Hardware=20 Software=20 Professional Services Horizontal Submarkets=20 Storage & Compute Infrastructure=20 Networking Infrastructure=20 Hadoop & Infrastructure Software=20 SQL=20 NoSQL=20 Analytic Platforms & Applications=20 Cloud Platforms=20 Professional Services Vertical Submarkets=20 Automotive, Aerospace & Transportation=20 Banking & Securities=20 Defense & Intelligence=20 Education=20 Healthcare & Pharmaceutical=20 Smart Cities & Intelligent Buildings=20 Insurance=20 Manufacturing & Natural Resources=20 Web, Media & Entertainment=20 Public Safety & Homeland Security=20 Public Services=20 Retail & Hospitality=20 Telecommunications=20 Utilities & Energy=20 Wholesale Trade=20 Others Regional Markets=20 Asia Pacific=20 Eastern Europe=20 Latin & Central America=20 Middle East & Africa=20 North America=20 Western Europe Country Markets Argentina, Australia, Brazil, Canada, China, Czech Republic, Denmark, Finla= nd, France, Germany, India, Indonesia, Israel, Italy, Japan, Malaysia, Mex= ico, Netherlands, Norway, Pakistan, Philippines, Poland, Qatar, Russia, Sau= di Arabia, Singapore, South Africa, South Korea, Spain, Sweden, Taiwan, Tha= iland, UAE, UK, USA=20 Report Pricing: =20 Single User License: USD 2,500 Company Wide License: USD 3,500 =20 Ordering Process: =20 Please provide the following information: Report Title - Big Data Market: 2017 =96 2030 Report License - (Single User/Company Wide) Name - Email - Job Title - Company - Invoice Address - Please contact me if you have any questions, or wish to purchase a copy. Ta= ble of contents, List of figures and List of companies mentioned in report = are given below for more inside. I look forward to hearing from you. =20 Kind Regards =20 Andy Silva Marketing Executive Signals and Systems Telecom andy.silva@snscommunication.com _________________________________________________________________________ Table of Contents: =20 1 Chapter 1: Introduction 1.1 Executive Summary 1.2 Topics Covered 1.3 Forecast Segmentation 1.4 Key Questions Answered 1.5 Key Findings 1.6 Methodology 1.7 Target Audience 1.8 Companies & Organizations Mentioned =20 2 Chapter 2: An Overview of Big Data 2.1 What is Big Data=3F 2.2 Key Approaches to Big Data Processing 2.2.1 Hadoop 2.2.2 NoSQL 2.2.3 MPAD (Massively Parallel Analytic Databases) 2.2.4 In-Memory Processing 2.2.5 Stream Processing Technologies 2.2.6 Spark 2.2.7 Other Databases & Analytic Technologies 2.3 Key Characteristics of Big Data 2.3.1 Volume 2.3.2 Velocity 2.3.3 Variety 2.3.4 Value 2.4 Market Growth Drivers 2.4.1 Awareness of Benefits 2.4.2 Maturation of Big Data Platforms 2.4.3 Continued Investments by Web Giants, Governments & Enterprises 2.4.4 Growth of Data Volume, Velocity & Variety 2.4.5 Vendor Commitments & Partnerships 2.4.6 Technology Trends Lowering Entry Barriers 2.5 Market Barriers 2.5.1 Lack of Analytic Specialists 2.5.2 Uncertain Big Data Strategies 2.5.3 Organizational Resistance to Big Data Adoption 2.5.4 Technical Challenges: Scalability & Maintenance 2.5.5 Security & Privacy Concerns =20 3 Chapter 3: Big Data Analytics 3.1 What are Big Data Analytics=3F 3.2 The Importance of Analytics 3.3 Reactive vs. Proactive Analytics 3.4 Customer vs. Operational Analytics 3.5 Technology & Implementation Approaches 3.5.1 Grid Computing 3.5.2 In-Database Processing 3.5.3 In-Memory Analytics 3.5.4 Machine Learning & Data Mining 3.5.5 Predictive Analytics 3.5.6 NLP (Natural Language Processing) 3.5.7 Text Analytics 3.5.8 Visual Analytics 3.5.9 Social Media, IT & Telco Network Analytics =20 4 Chapter 4: Big Data in Automotive, Aerospace & Transportation 4.1 Overview & Investment Potential 4.2 Key Applications 4.2.1 Autonomous Driving 4.2.2 Warranty Analytics for Automotive OEMs 4.2.3 Predictive Aircraft Maintenance & Fuel Optimization 4.2.4 Air Traffic Control 4.2.5 Transport Fleet Optimization 4.2.6 UBI (Usage Based Insurance) 4.3 Case Studies 4.3.1 Delphi Automotive: Monetizing Connected Vehicles with Big Data 4.3.2 Boeing: Making Flying More Efficient with Big Data 4.3.3 BMW: Eliminating Defects in New Vehicle Models with Big Data 4.3.4 Toyota Motor Corporation: Powering Smart Cars with Big Data 4.3.5 Ford Motor Company: Making Efficient Transportation Decisions with Bi= g Data =20 5 Chapter 5: Big Data in Banking & Securities 5.1 Overview & Investment Potential 5.2 Key Applications 5.2.1 Customer Retention & Personalized Product Offering 5.2.2 Risk Management 5.2.3 Fraud Detection 5.2.4 Credit Scoring 5.3 Case Studies 5.3.1 HSBC Group: Avoiding Regulatory Penalties with Big Data 5.3.2 JPMorgan Chase & Co.: Improving Business Processes with Big Data 5.3.3 OTP Bank: Reducing Loan Defaults with Big Data 5.3.4 CBA (Commonwealth Bank of Australia): Providing Personalized Services= with Big Data =20 6 Chapter 6: Big Data in Defense & Intelligence 6.1 Overview & Investment Potential 6.2 Key Applications 6.2.1 Intelligence Gathering 6.2.2 Battlefield Analytics 6.2.3 Energy Saving Opportunities in the Battlefield 6.2.4 Preventing Injuries on the Battlefield 6.3 Case Studies 6.3.1 U.S. Air Force: Providing Actionable Intelligence to Warfighters with= Big Data 6.3.2 Royal Navy: Empowering Submarine Warfare with Big Data 6.3.3 NSA (National Security Agency): Capitalizing on Big Data to Detect Th= reats 6.3.4 Ministry of State Security, China: Predictive Policing with Big Data 6.3.5 French DGSE (General Directorate for External Security): Enhancing In= telligence with Big Data =20 7 Chapter 7: Big Data in Education 7.1 Overview & Investment Potential 7.2 Key Applications 7.2.1 Information Integration 7.2.2 Identifying Learning Patterns 7.2.3 Enabling Student-Directed Learning 7.3 Case Studies 7.3.1 Purdue University: Ensuring Successful Higher Education Outcomes with= Big Data 7.3.2 Nottingham Trent University: Successful Student Outcomes with Big Data 7.3.3 Edith Cowen University: Increasing Student Retention with Big Data =20 8 Chapter 8: Big Data in Healthcare & Pharma 8.1 Overview & Investment Potential 8.2 Key Applications 8.2.1 Managing Population Health Efficiently 8.2.2 Improving Patient Care with Medical Data Analytics 8.2.3 Improving Clinical Development & Trials 8.2.4 Drug Development: Improving Time to Market 8.3 Case Studies 8.3.1 Amino: Healthcare Transparency with Big Data 8.3.2 Novartis: Digitizing Healthcare with Big Data 8.3.3 GSK (GlaxoSmithKline): Accelerating Drug Discovering with Big Data 8.3.4 Pfizer: Developing Effective and Targeted Therapies with Big Data 8.3.5 Roche: Personalizing Healthcare with Big Data 8.3.6 Sanofi: Proactive Diabetes Care with Big Data =20 9 Chapter 9: Big Data in Smart Cities & Intelligent Buildings 9.1 Overview & Investment Potential 9.2 Key Applications 9.2.1 Energy Optimization & Fault Detection 9.2.2 Intelligent Building Analytics 9.2.3 Urban Transportation Management 9.2.4 Optimizing Energy Production 9.2.5 Water Management 9.2.6 Urban Waste Management 9.3 Case Studies 9.3.1 Singapore: Building a Smart Nation with Big Data 9.3.2 Glasgow City Council: Promoting Smart City Efforts with Big Data 9.3.3 OVG Real Estate: Powering the World=92s Most Intelligent Building wit= h Big Data =20 10 Chapter 10: Big Data in Insurance 10.1 Overview & Investment Potential 10.2 Key Applications 10.2.1 Claims Fraud Mitigation 10.2.2 Customer Retention & Profiling 10.2.3 Risk Management 10.3 Case Studies 10.3.1 Zurich Insurance Group: Enhancing Risk Management with Big Data 10.3.2 RSA Group: Improving Customer Relations with Big Data 10.3.3 Primerica: Improving Insurance Sales Force Productivity with Big Data =20 11 Chapter 11: Big Data in Manufacturing & Natural Resources 11.1 Overview & Investment Potential 11.2 Key Applications 11.2.1 Asset Maintenance & Downtime Reduction 11.2.2 Quality & Environmental Impact Control 11.2.3 Optimized Supply Chain 11.2.4 Exploration & Identification of Natural Resources 11.3 Case Studies 11.3.1 Intel Corporation: Cutting Manufacturing Costs with Big Data 11.3.2 Dow Chemical Company: Optimizing Chemical Manufacturing with Big Data 11.3.3 Michelin: Improving the Efficiency of Supply Chain and Manufacturing= with Big Data 11.3.4 Brunei: Saving Natural Resources with Big Data =20 12 Chapter 12: Big Data in Web, Media & Entertainment 12.1 Overview & Investment Potential 12.2 Key Applications 12.2.1 Audience & Advertising Optimization 12.2.2 Channel Optimization 12.2.3 Recommendation Engines 12.2.4 Optimized Search 12.2.5 Live Sports Event Analytics 12.2.6 Outsourcing Big Data Analytics to Other Verticals 12.3 Case Studies 12.3.1 Netflix: Improving Viewership with Big Data 12.3.2 NFL (National Football League): Improving Stadium Experience with Bi= g Data 12.3.3 Walt Disney Company: Enhancing Theme Park Experience with Big Data 12.3.4 Baidu: Reshaping Search Capabilities with Big Data 12.3.5 Constant Contact: Effective Marketing with Big Data =20 13 Chapter 13: Big Data in Public Safety & Homeland Security 13.1 Overview & Investment Potential 13.2 Key Applications 13.2.1 Cyber Crime Mitigation 13.2.2 Crime Prediction Analytics 13.2.3 Video Analytics & Situational Awareness 13.3 Case Studies 13.3.1 DHS (U.S. Department of Homeland Security): Identifying Threats to P= hysical and Network Infrastructure with Big Data 13.3.2 Dubai Police: Locating Wanted Vehicles More Efficiently with Big Data 13.3.3 Memphis Police Department: Crime Reduction with Big Data =20 14 Chapter 14: Big Data in Public Services 14.1 Overview & Investment Potential 14.2 Key Applications 14.2.1 Public Sentiment Analysis 14.2.2 Tax Collection & Fraud Detection 14.2.3 Economic Analysis 14.2.4 Predicting & Mitigating Disasters 14.3 Case Studies 14.3.1 ONS (Office for National Statistics): Exploring the UK Economy with = Big Data 14.3.2 New York State Department of Taxation and Finance: Increasing Tax Re= venue with Big Data 14.3.3 Alameda County Social Services Agency: Benefit Fraud Reduction with = Big Data 14.3.4 City of Chicago: Improving Government Productivity with Big Data 14.3.5 FDNY (Fire Department of the City of New York): Fighting Fires with = Big Data 14.3.6 Ambulance Victoria: Improving Patient Survival Rates with Big Data =20 15 Chapter 15: Big Data in Retail, Wholesale & Hospitality 15.1 Overview & Investment Potential 15.2 Key Applications 15.2.1 Customer Sentiment Analysis 15.2.2 Customer & Branch Segmentation 15.2.3 Price Optimization 15.2.4 Personalized Marketing 15.2.5 Optimizing & Monitoring the Supply Chain 15.2.6 In-Field Sales Analytics 15.3 Case Studies 15.3.1 Walmart: Making Smarter Stocking Decision with Big Data 15.3.2 Tesco: Reducing Supermarket Energy Bills with Big Data 15.3.3 Marriott International: Elevating Guest Services with Big Data 15.3.4 JJ Food Service: Predictive Wholesale Shopping Lists with Big Data =20 16 Chapter 16: Big Data in Telecommunications 16.1 Overview & Investment Potential 16.2 Key Applications 16.2.1 Network Performance & Coverage Optimization 16.2.2 Customer Churn Prevention 16.2.3 Personalized Marketing 16.2.4 Tailored Location Based Services 16.2.5 Fraud Detection 16.3 Case Studies 16.3.1 BT Group: Hunting Down Nuisance Callers with Big Data 16.3.2 AT&T: Smart Network Management with Big Data 16.3.3 T-Mobile USA: Cutting Down Churn Rate with Big Data 16.3.4 TEOCO: Helping Service Providers Save Millions with Big Data 16.3.5 Freedom Mobile: Optimizing Video Quality with Big Data 16.3.6 Coriant: SaaS Based Analytics with Big Data =20 17 Chapter 17: Big Data in Utilities & Energy 17.1 Overview & Investment Potential 17.2 Key Applications 17.2.1 Customer Retention 17.2.2 Forecasting Energy 17.2.3 Billing Analytics 17.2.4 Predictive Maintenance 17.2.5 Maximizing the Potential of Drilling 17.2.6 Production Optimization 17.3 Case Studies 17.3.1 Royal Dutch Shell: Developing Data-Driven Oil Fields with Big Data 17.3.2 British Gas: Improving Customer Service with Big Data 17.3.3 Oncor Electric Delivery: Intelligent Power Grid Management with Big = Data =20 18 Chapter 18: Big Data Industry Roadmap & Value Chain 18.1 Big Data Industry Roadmap 18.1.1 2017 =96 2020: Investments in Predictive Analytics & SaaS-Based Big = Data Offerings 18.1.2 2020 =96 2025: Growing Focus on Cognitive & Personalized Analytics 18.1.3 2025 =96 2030: Convergence with Future IoT Applications 18.2 The Big Data Value Chain 18.2.1 Hardware Providers 18.2.1.1 Storage & Compute Infrastructure Providers 18.2.1.2 Networking Infrastructure Providers 18.2.2 Software Providers 18.2.2.1 Hadoop & Infrastructure Software Providers 18.2.2.2 SQL & NoSQL Providers 18.2.2.3 Analytic Platform & Application Software Providers 18.2.2.4 Cloud Platform Providers 18.2.3 Professional Services Providers 18.2.4 End-to-End Solution Providers 18.2.5 Vertical Enterprises =20 19 Chapter 19: Standardization & Regulatory Initiatives 19.1 ASF (Apache Software Foundation) 19.1.1 Management of Hadoop 19.1.2 Big Data Projects Beyond Hadoop 19.2 CSA (Cloud Security Alliance) 19.2.1 BDWG (Big Data Working Group) 19.3 CSCC (Cloud Standards Customer Council) 19.3.1 Big Data Working Group 19.4 DMG (Data Mining Group) 19.4.1 PMML (Predictive Model Markup Language) Working Group 19.4.2 PFA (Portable Format for Analytics) Working Group 19.5 IEEE (Institute of Electrical and Electronics Engineers) =96Big Data I= nitiative 19.6 INCITS (InterNational Committee for Information Technology Standards) 19.6.1 Big Data Technical Committee 19.7 ISO (International Organization for Standardization) 19.7.1 ISO/IEC JTC 1/SC 32: Data Management and Interchange 19.7.2 ISO/IEC JTC 1/SC 38: Cloud Computing and Distributed Platforms 19.7.3 ISO/IEC JTC 1/SC 27: IT Security Techniques 19.7.4 ISO/IEC JTC 1/WG 9: Big Data 19.7.5 Collaborations with Other ISO Work Groups 19.8 ITU (International Telecommunications Union) 19.8.1 ITU-T Y.3600: Big Data =96 Cloud Computing Based Requirements and Ca= pabilities 19.8.2 Other Deliverables Through SG (Study Group) 13 on Future Networks 19.8.3 Other Relevant Work 19.9 Linux Foundation 19.9.1 ODPi (Open Ecosystem of Big Data) 19.10 NIST (National Institute of Standards and Technology) 19.10.1 NBD-PWG (NIST Big Data Public Working Group) 19.11 OASIS (Organization for the Advancement of Structured Information Sta= ndards) 19.11.1 Technical Committees 19.12 ODaF (Open Data Foundation) 19.12.1 Big Data Accessibility 19.13 ODCA (Open Data Center Alliance) 19.13.1 Work on Big Data 19.14 OGC (Open Geospatial Consortium) 19.14.1 Big Data DWG (Domain Working Group) 19.15 TM Forum 19.15.1 Big Data Analytics Strategic Program 19.16 TPC (Transaction Processing Performance Council) 19.16.1 TPC-BDWG (TPC Big Data Working Group) 19.17 W3C (World Wide Web Consortium) 19.17.1 Big Data Community Group 19.17.2 Open Government Community Group =20 20 Chapter 20: Market Analysis & Forecasts 20.1 Global Outlook for the Big Data Market 20.2 Submarket Segmentation 20.2.1 Storage and Compute Infrastructure 20.2.2 Networking Infrastructure 20.2.3 Hadoop & Infrastructure Software 20.2.4 SQL 20.2.5 NoSQL 20.2.6 Analytic Platforms & Applications 20.2.7 Cloud Platforms 20.2.8 Professional Services 20.3 Vertical Market Segmentation 20.3.1 Automotive, Aerospace & Transportation 20.3.2 Banking & Securities 20.3.3 Defense & Intelligence 20.3.4 Education 20.3.5 Healthcare & Pharmaceutical 20.3.6 Smart Cities & Intelligent Buildings 20.3.7 Insurance 20.3.8 Manufacturing & Natural Resources 20.3.9 Media & Entertainment 20.3.10 Public Safety & Homeland Security 20.3.11 Public Services 20.3.12 Retail, Wholesale & Hospitality 20.3.13 Telecommunications 20.3.14 Utilities & Energy 20.3.15 Other Sectors 20.4 Regional Outlook 20.5 Asia Pacific 20.5.1 Country Level Segmentation 20.5.2 Australia 20.5.3 China 20.5.4 India 20.5.5 Indonesia 20.5.6 Japan 20.5.7 Malaysia 20.5.8 Pakistan 20.5.9 Philippines 20.5.10 Singapore 20.5.11 South Korea 20.5.12 Taiwan 20.5.13 Thailand 20.5.14 Rest of Asia Pacific 20.6 Eastern Europe 20.6.1 Country Level Segmentation 20.6.2 Czech Republic 20.6.3 Poland 20.6.4 Russia 20.6.5 Rest of Eastern Europe 20.7 Latin & Central America 20.7.1 Country Level Segmentation 20.7.2 Argentina 20.7.3 Brazil 20.7.4 Mexico 20.7.5 Rest of Latin & Central America 20.8 Middle East & Africa 20.8.1 Country Level Segmentation 20.8.2 Israel 20.8.3 Qatar 20.8.4 Saudi Arabia 20.8.5 South Africa 20.8.6 UAE 20.8.7 Rest of the Middle East & Africa 20.9 North America 20.9.1 Country Level Segmentation 20.9.2 Canada 20.9.3 USA 20.10 Western Europe 20.10.1 Country Level Segmentation 20.10.2 Denmark 20.10.3 Finland 20.10.4 France 20.10.5 Germany 20.10.6 Italy 20.10.7 Netherlands 20.10.8 Norway 20.10.9 Spain 20.10.10 Sweden 20.10.11 UK 20.10.12 Rest of Western Europe =20 21 Chapter 21: Vendor Landscape 21.1 1010data 21.2 Absolutdata 21.3 Accenture 21.4 Actian Corporation 21.5 Adaptive Insights 21.6 Advizor Solutions 21.7 AeroSpike 21.8 AFS Technologies 21.9 Alation 21.10 Algorithmia 21.11 Alluxio 21.12 Alpine Data 21.13 Alteryx 21.14 AMD (Advanced Micro Devices) 21.15 Apixio 21.16 Arcadia Data 21.17 Arimo 21.18 ARM 21.19 AtScale 21.20 Attivio 21.21 Attunity 21.22 Automated Insights 21.23 AWS (Amazon Web Services) 21.24 Axiomatics 21.25 Ayasdi 21.26 Basho Technologies 21.27 BCG (Boston Consulting Group) 21.28 Bedrock Data 21.29 BetterWorks 21.30 Big Cloud Analytics 21.31 Big Panda 21.32 Birst 21.33 Bitam 21.34 Blue Medora 21.35 BlueData Software 21.36 BlueTalon 21.37 BMC Software 21.38 BOARD International 21.39 Booz Allen Hamilton 21.40 Boxever 21.41 CACI International 21.42 Cambridge Semantics 21.43 Capgemini 21.44 Cazena 21.45 Centrifuge Systems 21.46 CenturyLink 21.47 Chartio 21.48 Cisco Systems 21.49 Civis Analytics 21.50 ClearStory Data 21.51 Cloudability 21.52 Cloudera 21.53 Clustrix 21.54 CognitiveScale 21.55 Collibra 21.56 Concurrent Computer Corporation 21.57 Confluent 21.58 Contexti 21.59 Continuum Analytics 21.60 Couchbase 21.61 CrowdFlower 21.62 Databricks 21.63 DataGravity 21.64 Dataiku 21.65 Datameer 21.66 DataRobot 21.67 DataScience 21.68 DataStax 21.69 DataTorrent 21.70 Datawatch Corporation 21.71 Datos IO 21.72 DDN (DataDirect Networks) 21.73 Decisyon 21.74 Dell Technologies 21.75 Deloitte 21.76 Demandbase 21.77 Denodo Technologies 21.78 Digital Reasoning Systems 21.79 Dimensional Insight 21.80 Dolphin Enterprise Solutions Corporation 21.81 Domino Data Lab 21.82 Domo 21.83 DriveScale 21.84 Dundas Data Visualization 21.85 DXC Technology 21.86 Eligotech 21.87 Engineering Group (Engineering Ingegneria Informatica) 21.88 EnterpriseDB 21.89 eQ Technologic 21.90 Ericsson 21.91 EXASOL 21.92 Facebook 21.93 FICO (Fair Isaac Corporation) 21.94 Fractal Analytics 21.95 Fujitsu 21.96 Fuzzy Logix 21.97 Gainsight 21.98 GE (General Electric) 21.99 Glassbeam 21.100 GoodData Corporation 21.101 Google 21.102 Greenwave Systems 21.103 GridGain Systems 21.104 Guavus 21.105 H2O.ai 21.106 HDS (Hitachi Data Systems) 21.107 Hedvig 21.108 Hortonworks 21.109 HPE (Hewlett Packard Enterprise) 21.110 Huawei 21.111 IBM Corporation 21.112 iDashboards 21.113 Impetus Technologies 21.114 Incorta 21.115 InetSoft Technology Corporation 21.116 Infer 21.117 Infor 21.118 Informatica Corporation 21.119 Information Builders 21.120 Infosys 21.121 Infoworks 21.122 Insightsoftware.com 21.123 InsightSquared 21.124 Intel Corporation 21.125 Interana 21.126 InterSystems Corporation 21.127 Jedox 21.128 Jethro 21.129 Jinfonet Software 21.130 Juniper Networks 21.131 KALEAO 21.132 Keen IO 21.133 Kinetica 21.134 KNIME 21.135 Kognitio 21.136 Kyvos Insights 21.137 Lavastorm 21.138 Lexalytics 21.139 Lexmark International 21.140 Logi Analytics 21.141 Longview Solutions 21.142 Looker Data Sciences 21.143 LucidWorks 21.144 Luminoso Technologies 21.145 Maana 21.146 Magento Commerce 21.147 Manthan Software Services 21.148 MapD Technologies 21.149 MapR Technologies 21.150 MariaDB Corporation 21.151 MarkLogic Corporation 21.152 Mathworks 21.153 MemSQL 21.154 Metric Insights 21.155 Microsoft Corporation 21.156 MicroStrategy 21.157 Minitab 21.158 MongoDB 21.159 Mu Sigma 21.160 Neo Technology 21.161 NetApp 21.162 Nimbix 21.163 Nokia 21.164 NTT Data Corporation 21.165 Numerify 21.166 NuoDB 21.167 Nutonian 21.168 NVIDIA Corporation 21.169 Oblong Industries 21.170 OpenText Corporation 21.171 Opera Solutions 21.172 Optimal Plus 21.173 Oracle Corporation 21.174 Palantir Technologies 21.175 Panorama Software 21.176 Paxata 21.177 Pentaho Corporation 21.178 Pepperdata 21.179 Phocas Software 21.180 Pivotal Software 21.181 Prognoz 21.182 Progress Software Corporation 21.183 PwC (PricewaterhouseCoopers International) 21.184 Pyramid Analytics 21.185 Qlik 21.186 Quantum Corporation 21.187 Qubole 21.188 Rackspace 21.189 Radius Intelligence 21.190 RapidMiner 21.191 Recorded Future 21.192 Red Hat 21.193 Redis Labs 21.194 RedPoint Global 21.195 Reltio 21.196 RStudio 21.197 Ryft Systems 21.198 Sailthru 21.199 Salesforce.com 21.200 Salient Management Company 21.201 Samsung Group 21.202 SAP 21.203 SAS Institute 21.204 ScaleDB 21.205 ScaleOut Software 21.206 SCIO Health Analytics 21.207 Seagate Technology 21.208 Sinequa 21.209 SiSense 21.210 SnapLogic 21.211 Snowflake Computing 21.212 Software AG 21.213 Splice Machine 21.214 Splunk 21.215 Sqrrl 21.216 Strategy Companion Corporation 21.217 StreamSets 21.218 Striim 21.219 Sumo Logic 21.220 Supermicro (Super Micro Computer) 21.221 Syncsort 21.222 SynerScope 21.223 Tableau Software 21.224 Talena 21.225 Talend 21.226 Tamr 21.227 TARGIT 21.228 TCS (Tata Consultancy Services) 21.229 Teradata Corporation 21.230 ThoughtSpot 21.231 TIBCO Software 21.232 Tidemark 21.233 Toshiba Corporation 21.234 Trifacta 21.235 Unravel Data 21.236 VMware 21.237 VoltDB 21.238 Waterline Data 21.239 Western Digital Corporation 21.240 WiPro 21.241 Workday 21.242 Xplenty 21.243 Yellowfin International 21.244 Yseop 21.245 Zendesk 21.246 Zoomdata 21.247 Zucchetti =20 22 Chapter 22: Conclusion & Strategic Recommendations 22.1 Big Data Technology: Beyond Data Capture & Analytics 22.2 Transforming IT from a Cost Center to a Profit Center 22.3 Can Privacy Implications Hinder Success=3F 22.4 Maximizing Innovation with Careful Regulation 22.5 Battling Organizational & Data Silos 22.6 Moving Big Data to the Cloud 22.7 Software vs. Hardware Investments 22.8 Vendor Share: Who Leads the Market=3F 22.9 Moving Towards Consolidation: Review of M&A Activity in the Vendor Are= na 22.10 Big Data Driving Wider IT Industry Investments 22.11 Assessing the Impact of IoT & M2M 22.12 Recommendations 22.12.1 Big Data Hardware, Software & Professional Services Providers 22.12.2 Enterprises =20 List of Figures: =20 Figure 1: Hadoop Architecture Figure 2: Reactive vs. Proactive Analytics Figure 3: Big Data Industry Roadmap Figure 4: Big Data Value Chain Figure 5: Key Aspects of Big Data Standardization Figure 6: Global Big Data Revenue: 2017 - 2030 ($ Million) Figure 7: Global Big Data Revenue by Submarket: 2017 - 2030 ($ Million) Figure 8: Global Big Data Storage and Compute Infrastructure Submarket Reve= nue: 2017 - 2030 ($ Million) Figure 9: Global Big Data Networking Infrastructure Submarket Revenue: 2017= - 2030 ($ Million) Figure 10: Global Big Data Hadoop & Infrastructure Software Submarket Reven= ue: 2017 - 2030 ($ Million) Figure 11: Global Big Data SQL Submarket Revenue: 2017 - 2030 ($ Million) Figure 12: Global Big Data NoSQL Submarket Revenue: 2017 - 2030 ($ Million) Figure 13: Global Big Data Analytic Platforms & Applications Submarket Reve= nue: 2017 - 2030 ($ Million) Figure 14: Global Big Data Cloud Platforms Submarket Revenue: 2017 - 2030 (= $ Million) Figure 15: Global Big Data Professional Services Submarket Revenue: 2017 - = 2030 ($ Million) Figure 16: Global Big Data Revenue by Vertical Market: 2017 - 2030 ($ Milli= on) Figure 17: Global Big Data Revenue in the Automotive, Aerospace & Transport= ation Sector: 2017 - 2030 ($ Million) Figure 18: Global Big Data Revenue in the Banking & Securities Sector: 2017= - 2030 ($ Million) Figure 19: Global Big Data Revenue in the Defense & Intelligence Sector: 20= 17 - 2030 ($ Million) Figure 20: Global Big Data Revenue in the Education Sector: 2017 - 2030 ($ = Million) Figure 21: Global Big Data Revenue in the Healthcare & Pharmaceutical Secto= r: 2017 - 2030 ($ Million) Figure 22: Global Big Data Revenue in the Smart Cities & Intelligent Buildi= ngs Sector: 2017 - 2030 ($ Million) Figure 23: Global Big Data Revenue in the Insurance Sector: 2017 - 2030 ($ = Million) Figure 24: Global Big Data Revenue in the Manufacturing & Natural Resources= Sector: 2017 - 2030 ($ Million) Figure 25: Global Big Data Revenue in the Media & Entertainment Sector: 201= 7 - 2030 ($ Million) Figure 26: Global Big Data Revenue in the Public Safety & Homeland Security= Sector: 2017 - 2030 ($ Million) Figure 27: Global Big Data Revenue in the Public Services Sector: 2017 - 20= 30 ($ Million) Figure 28: Global Big Data Revenue in the Retail, Wholesale & Hospitality S= ector: 2017 - 2030 ($ Million) Figure 29: Global Big Data Revenue in the Telecommunications Sector: 2017 -= 2030 ($ Million) Figure 30: Global Big Data Revenue in the Utilities & Energy Sector: 2017 -= 2030 ($ Million) Figure 31: Global Big Data Revenue in Other Vertical Sectors: 2017 - 2030 (= $ Million) Figure 32: Big Data Revenue by Region: 2017 - 2030 ($ Million) Figure 33: Asia Pacific Big Data Revenue: 2017 - 2030 ($ Million) Figure 34: Asia Pacific Big Data Revenue by Country: 2017 - 2030 ($ Million) Figure 35: Australia Big Data Revenue: 2017 - 2030 ($ Million) Figure 36: China Big Data Revenue: 2017 - 2030 ($ Million) Figure 37: India Big Data Revenue: 2017 - 2030 ($ Million) Figure 38: Indonesia Big Data Revenue: 2017 - 2030 ($ Million) Figure 39: Japan Big Data Revenue: 2017 - 2030 ($ Million) Figure 40: Malaysia Big Data Revenue: 2017 - 2030 ($ Million) Figure 41: Pakistan Big Data Revenue: 2017 - 2030 ($ Million) Figure 42: Philippines Big Data Revenue: 2017 - 2030 ($ Million) Figure 43: Singapore Big Data Revenue: 2017 - 2030 ($ Million) Figure 44: South Korea Big Data Revenue: 2017 - 2030 ($ Million) Figure 45: Taiwan Big Data Revenue: 2017 - 2030 ($ Million) Figure 46: Thailand Big Data Revenue: 2017 - 2030 ($ Million) Figure 47: Big Data Revenue in the Rest of Asia Pacific: 2017 - 2030 ($ Mil= lion) Figure 48: Eastern Europe Big Data Revenue: 2017 - 2030 ($ Million) Figure 49: Eastern Europe Big Data Revenue by Country: 2017 - 2030 ($ Milli= on) Figure 50: Czech Republic Big Data Revenue: 2017 - 2030 ($ Million) Figure 51: Poland Big Data Revenue: 2017 - 2030 ($ Million) Figure 52: Russia Big Data Revenue: 2017 - 2030 ($ Million) Figure 53: Big Data Revenue in the Rest of Eastern Europe: 2017 - 2030 ($ M= illion) Figure 54: Latin & Central America Big Data Revenue: 2017 - 2030 ($ Million) Figure 55: Latin & Central America Big Data Revenue by Country: 2017 - 2030= ($ Million) Figure 56: Argentina Big Data Revenue: 2017 - 2030 ($ Million) Figure 57: Brazil Big Data Revenue: 2017 - 2030 ($ Million) Figure 58: Mexico Big Data Revenue: 2017 - 2030 ($ Million) Figure 59: Big Data Revenue in the Rest of Latin & Central America: 2017 - = 2030 ($ Million) Figure 60: Middle East & Africa Big Data Revenue: 2017 - 2030 ($ Million) Figure 61: Middle East & Africa Big Data Revenue by Country: 2017 - 2030 ($= Million) Figure 62: Israel Big Data Revenue: 2017 - 2030 ($ Million) Figure 63: Qatar Big Data Revenue: 2017 - 2030 ($ Million) Figure 64: Saudi Arabia Big Data Revenue: 2017 - 2030 ($ Million) Figure 65: South Africa Big Data Revenue: 2017 - 2030 ($ Million) Figure 66: UAE Big Data Revenue: 2017 - 2030 ($ Million) Figure 67: Big Data Revenue in the Rest of the Middle East & Africa: 2017 -= 2030 ($ Million) Figure 68: North America Big Data Revenue: 2017 - 2030 ($ Million) Figure 69: North America Big Data Revenue by Country: 2017 - 2030 ($ Millio= n) Figure 70: Canada Big Data Revenue: 2017 - 2030 ($ Million) Figure 71: USA Big Data Revenue: 2017 - 2030 ($ Million) Figure 72: Western Europe Big Data Revenue: 2017 - 2030 ($ Million) Figure 73: Western Europe Big Data Revenue by Country: 2017 - 2030 ($ Milli= on) Figure 74: Denmark Big Data Revenue: 2017 - 2030 ($ Million) Figure 75: Finland Big Data Revenue: 2017 - 2030 ($ Million) Figure 76: France Big Data Revenue: 2017 - 2030 ($ Million) Figure 77: Germany Big Data Revenue: 2017 - 2030 ($ Million) Figure 78: Italy Big Data Revenue: 2017 - 2030 ($ Million) Figure 79: Netherlands Big Data Revenue: 2017 - 2030 ($ Million) Figure 80: Norway Big Data Revenue: 2017 - 2030 ($ Million) Figure 81: Spain Big Data Revenue: 2017 - 2030 ($ Million) Figure 82: Sweden Big Data Revenue: 2017 - 2030 ($ Million) Figure 83: UK Big Data Revenue: 2017 - 2030 ($ Million) Figure 84: Big Data Revenue in the Rest of Western Europe: 2017 - 2030 ($ M= illion) Figure 85: Global Big Data Workload Distribution by Environment: 2017 - 203= 0 (%) Figure 86: Global Big Data Revenue by Hardware, Software & Professional Ser= vices: 2017 - 2030 ($ Million) Figure 87: Big Data Vendor Market Share (%) Figure 88: Global IT Expenditure Driven by Big Data Investments: 2017 - 203= 0 ($ Million) Figure 89: Global M2M Connections by Access Technology: 2017 - 2030 (Millio= ns) =20 Thank you once again and looking forward to hearing from you. =20 Kind Regards =20 Andy Silva Marketing Executive Signals and Systems Telecom andy.silva@snscommunication.com =20 =20 To unsubscribe send an email with unsubscribe in the subject line to: remov= e@snsreports.com =20 From owner-freebsd-ppc@freebsd.org Wed May 3 14:27:52 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 5995BD5A16D for ; Wed, 3 May 2017 14:27:52 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-63.reflexion.net [208.70.210.63]) (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 1F3D3960 for ; Wed, 3 May 2017 14:27:51 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 27204 invoked from network); 3 May 2017 14:31:08 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 3 May 2017 14:31:08 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.40.0) with SMTP; Wed, 03 May 2017 10:27:50 -0400 (EDT) Received: (qmail 29847 invoked from network); 3 May 2017 14:27:50 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 3 May 2017 14:27:50 -0000 Received: from [192.168.1.106] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 6E600EC8FD9; Wed, 3 May 2017 07:27:49 -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.3 \(3273\)) Subject: FYI: head -r317729 for powerpc (via clang) gets "clang frontend command failed due to signal" Message-Id: Date: Wed, 3 May 2017 07:27:48 -0700 To: FreeBSD Toolchain , FreeBSD PowerPC ML X-Mailer: Apple Mail (2.3273) 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: Wed, 03 May 2017 14:27:52 -0000 I've made a llvm bugzilla submittal for the following: 32908 Attempting a buildworld buildkernel for TARGET_ARCH=3Dpowerpc for head -r317729 got. . . --- all_subdir_mpt --- Building = /usr/obj/powerpcvtsc_clang/powerpc.powerpc/usr/src/sys/GENERICvtsc-NODBG/m= odules/usr/src/sys/modules/mpt/mpt_cam.o --- mpt_cam.o --- cc: error: unable to execute command: Segmentation fault (core dumped) --- all_subdir_mqueue --- =3D=3D=3D> mqueue (all) --- all_subdir_mpt --- cc: error: clang frontend command failed due to signal (use -v to see = invocation) FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on = LLVM 4.0.0) Target: powerpc-unknown-freebsd12.0 Thread model: posix InstalledDir: = /usr/obj/powerpcvtsc_clang/powerpc.powerpc/usr/src/tmp/usr/bin cc: note: diagnostic msg: PLEASE submit a bug report to = https://bugs.freebsd.org/submit/ and include the crash backtrace, = preprocessed source, and associated run script. --- all_subdir_mpt --- cc: note: diagnostic msg:=20 ******************** PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT: Preprocessed source(s) and associated run script(s) are located at: cc: note: diagnostic msg: /tmp/mpt_cam-56fad4.c cc: note: diagnostic msg: /tmp/mpt_cam-56fad4.sh cc: note: diagnostic msg:=20 ******************** *** [mpt_cam.o] Error code 254 make[4]: stopped in /usr/src/sys/modules/mpt .ERROR_TARGET=3D'mpt_cam.o' = .ERROR_META_FILE=3D'/usr/obj/powerpcvtsc_clang/powerpc.powerpc/usr/src/sys= /GENERICvtsc-NODBG/modules/usr/src/sys/modules/mpt/mpt_cam.o.meta' # ls -lTt /tmp/mpt* -rw-r--r-- 1 root wheel 4894 May 3 06:58:09 2017 = /tmp/mpt_cam-56fad4.sh -rw-r--r-- 1 root wheel 1855254 May 3 06:58:09 2017 = /tmp/mpt_cam-56fad4.c # more = /usr/obj/powerpcvtsc_clang/powerpc.powerpc/usr/src/sys/GENERICvtsc-NODBG/m= odules/usr/src/sys/modules/mpt/mpt_cam.o.meta # Meta data file = /usr/obj/powerpcvtsc_clang/powerpc.powerpc/usr/src/sys/GENERICvtsc-NODBG/m= odules/usr/src/sys/modules/mpt/mpt_cam.o.meta CMD cc -target powerpc-unknown-freebsd12.0 = --sysroot=3D/usr/obj/powerpcvtsc_clang/powerpc.powerpc/usr/src/tmp = -B/usr/obj/powerpcvtsc_clang/powerpc.powerpc/usr/src/tmp/usr/bin -O2 = -pipe -fno-strict-aliasing -D_KERNEL -DKLD_MODULE -nostdinc = -DHAVE_KERNEL_OPTION_HEADERS -include = /usr/obj/powerpcvtsc_clang/powerpc.powerpc/usr/src/sys/GENERICvtsc-NODBG/o= pt_global.h -I. -I/usr/src/sys -fno-common -g -fno-omit-frame-pointer = -I/usr/obj/powerpcvtsc_clang/powerpc.powerpc/usr/src/sys/GENERICvtsc-NODBG= -mno-altivec -msoft-float -ffreestanding -fwrapv -fstack-protector = -gdwarf-2 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes = -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef = -Wno-pointer-sign -D__printf__=3D__freebsd_kprintf__ = -Wmissing-include-dirs -fdiagnostics-show-option -Wno-unknown-pragmas = -Wno-error-tautological-compare -Wno-error-empty-body = -Wno-error-parentheses-equality -Wno-error-unused-function = -Wno-error-pointer-sign -Wno-error-shift-negative-value = -Wno-error-address-of-packed-member -std=3Diso9899:1999 -c = /usr/src/sys/dev/mpt/mpt_cam.c -o mpt_cam.o CMD ctfconvert -L VERSION -g mpt_cam.o CWD = /usr/obj/powerpcvtsc_clang/powerpc.powerpc/usr/src/sys/GENERICvtsc-NODBG/m= odules/usr/src/sys/modules/mpt TARGET mpt_cam.o -- command output -- cc: error: unable to execute command: Segmentation fault (core dumped) cc: error: clang frontend command failed due to signal (use -v to see = invocation) FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on = LLVM 4.0.0) Target: powerpc-unknown-freebsd12.0 Thread model: posix InstalledDir: = /usr/obj/powerpcvtsc_clang/powerpc.powerpc/usr/src/tmp/usr/bin cc: note: diagnostic msg: PLEASE submit a bug report to = https://bugs.freebsd.org/submit/ and include the crash backtrace, = preprocessed source, and associated run script. cc: note: diagnostic msg:=20 ******************** PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT: Preprocessed source(s) and associated run script(s) are located at: cc: note: diagnostic msg: /tmp/mpt_cam-56fad4.c cc: note: diagnostic msg: /tmp/mpt_cam-56fad4.sh cc: note: diagnostic msg:=20 ******************** *** Error code 254 # more /tmp/mpt_cam-56fad4.sh # Crash reproducer for FreeBSD clang version 4.0.0 = (tags/RELEASE_400/final 297347) (based on LLVM 4.0.0) # Driver args: "--target=3Dpowerpc-unknown-freebsd12.0" = "--sysroot=3D/usr/obj/powerpcvtsc_clang/powerpc.powerpc/usr/src/tmp" = "-B" "/usr/obj/powerpcvtsc_clang/powerpc.powerpc/usr/src/tmp/usr/bin" = "-O2" "-pipe" "-fno-strict-aliasing" "-D" "_KERNEL" "-D" "KLD_MODULE" = "-nostdinc" "-D" "HAVE_KERNEL_OPTION_HEADERS" "-include" = "/usr/obj/powerpcvtsc_clang/powerpc.powerpc/usr/src/sys/GENERICvtsc-NODBG/= opt_global.h" "-I" "." "-I" "/usr/src/sys" "-fno-common" "-g" = "-fno-omit-frame-pointer" "-I" = "/usr/obj/powerpcvtsc_clang/powerpc.powerpc/usr/src/sys/GENERICvtsc-NODBG"= "-fno-altivec" "-msoft-float" "-ffreestanding" "-fwrapv" = "-fstack-protector" "-gdwarf-2" "-Wall" "-Wredundant-decls" = "-Wnested-externs" "-Wstrict-prototypes" "-Wmissing-prototypes" = "-Wpointer-arith" "-Winline" "-Wcast-qual" "-Wundef" "-Wno-pointer-sign" = "-D" "__printf__=3D__freebsd_kprintf__" "-Wmissing-include-dirs" = "-fdiagnostics-show-option" "-Wno-unknown-pragmas" = "-Wno-error-tautological-compare" "-Wno-error-empty-body" = "-Wno-error-parentheses-equality" "-Wno-error-unused-function" = "-Wno-error-pointer-sign" "-Wno-error-shift-negative-value" = "-Wno-error-address-of-packed-member" "-std=3Diso9899:1999" "-c" = "/usr/src/sys/dev/mpt/mpt_cam.c" "-o" "mpt_cam.o" # Original command: = "/usr/obj/powerpcvtsc_clang/powerpc.powerpc/usr/src/tmp/usr/bin/cc" = "-cc1" "-triple" "powerpc-unknown-freebsd12.0" "-emit-obj" = "-disable-free" "-main-file-name" "mpt_cam.c" "-mrelocation-model" = "static" "-mthread-model" "posix" "-mdisable-fp-elim" = "-relaxed-aliasing" "-masm-verbose" "-mconstructor-aliases" = "-target-cpu" "ppc" "-target-feature" "-hard-float" "-target-feature" = "-altivec" "-msoft-float" "-mfloat-abi" "soft" "-dwarf-column-info" = "-debug-info-kind=3Dstandalone" "-dwarf-version=3D2" = "-debugger-tuning=3Dgdb" "-coverage-notes-file" = "/usr/obj/powerpcvtsc_clang/powerpc.powerpc/usr/src/sys/GENERICvtsc-NODBG/= modules/usr/src/sys/modules/mpt/mpt_cam.gcno" "-nostdsysteminc" = "-nobuiltininc" "-resource-dir" = "/usr/obj/powerpcvtsc_clang/powerpc.powerpc/usr/src/tmp/usr/bin/../lib/cla= ng/4.0.0" "-include" = "/usr/obj/powerpcvtsc_clang/powerpc.powerpc/usr/src/sys/GENERICvtsc-NODBG/= opt_global.h" "-D" "_KERNEL" "-D" "KLD_MODULE" "-D" = "HAVE_KERNEL_OPTION_HEADERS" "-I" "." "-I" "/usr/src/sys" "-I" = "/usr/obj/powerpcvtsc_clang/powerpc.powerpc/usr/src/sys/GENERICvtsc-NODBG"= "-D" "__printf__=3D__freebsd_kprintf__" "-isysroot" = "/usr/obj/powerpcvtsc_clang/powerpc.powerpc/usr/src/tmp" "-O2" "-Wall" = "-Wredundant-decls" "-Wnested-externs" "-Wstrict-prototypes" = "-Wmissing-prototypes" "-Wpointer-arith" "-Winline" "-Wcast-qual" = "-Wundef" "-Wno-pointer-sign" "-Wmissing-include-dirs" = "-Wno-unknown-pragmas" "-Wno-error-tautological-compare" = "-Wno-error-empty-body" "-Wno-error-parentheses-equality" = "-Wno-error-unused-function" "-Wno-error-pointer-sign" = "-Wno-error-shift-negative-value" "-Wno-error-address-of-packed-member" = "-std=3Diso9899:1999" "-fdebug-compilation-dir" = "/usr/obj/powerpcvtsc_clang/powerpc.powerpc/usr/src/sys/GENERICvtsc-NODBG/= modules/usr/src/sys/modules/mpt" "-ferror-limit" "19" "-fmessage-length" = "0" "-ffreestanding" "-fwrapv" "-stack-protector" "1" "-fno-signed-char" = "-fobjc-runtime=3Dgnustep" "-fno-common" "-fdiagnostics-show-option" = "-vectorize-loops" "-vectorize-slp" "-o" "mpt_cam.o" "-x" "c" = "/usr/src/sys/dev/mpt/mpt_cam.c" "/usr/obj/powerpcvtsc_clang/powerpc.powerpc/usr/src/tmp/usr/bin/cc" = "-cc1" "-triple" "powerpc-unknown-freebsd12.0" "-emit-obj" = "-disable-free" "-main-file-name" "mpt_cam.c" "-mrelocation-model" = "static" "-mthread-model" "posix" "-mdisable-fp-elim" = "-relaxed-aliasing" "-masm-verbose" "-mconstructor-aliases" = "-target-cpu" "ppc" "-target-feature" "-hard-float" "-target-feature" = "-altivec" "-msoft-float" "-mfloat-abi" "soft" "-dwarf-column-info" = "-debug-info-kind=3Dstandalone" "-dwarf-version=3D2" = "-debugger-tuning=3Dgdb" "-coverage-notes-file" = "/usr/obj/powerpcvtsc_clang/powerpc.powerpc/usr/src/sys/GENERICvtsc-NODBG/= modules/usr/src/sys/modules/mpt/mpt_cam.gcno" "-nostdsysteminc" = "-nobuiltininc" "-D" "_KERNEL" "-D" "KLD_MODULE" "-D" = "HAVE_KERNEL_OPTION_HEADERS" "-D" "__printf__=3D__freebsd_kprintf__" = "-O2" "-Wall" "-Wredundant-decls" "-Wnested-externs" = "-Wstrict-prototypes" "-Wmissing-prototypes" "-Wpointer-arith" = "-Winline" "-Wcast-qual" "-Wundef" "-Wno-pointer-sign" = "-Wmissing-include-dirs" "-Wno-unknown-pragmas" = "-Wno-error-tautological-compare" "-Wno-error-empty-body" = "-Wno-error-parentheses-equality" "-Wno-error-unused-function" = "-Wno-error-pointer-sign" "-Wno-error-shift-negative-value" = "-Wno-error-address-of-packed-member" "-std=3Diso9899:1999" = "-ferror-limit" "19" "-fmessage-length" "0" "-ffreestanding" "-fwrapv" = "-stack-protector" "1" "-fno-signed-char" "-fobjc-runtime=3Dgnustep" = "-fno-common" "-fdiagnostics-show-option" "-vectorize-loops" = "-vectorize-slp" "-x" "c" "mpt_cam-56fad4.c" (The clang self-saved .c is too big to be here. A .xz variant is in llvm's 32908 .) =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Thu May 4 19:46:05 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 2DB6ED5D36F for ; Thu, 4 May 2017 19:46:05 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-77.reflexion.net [208.70.210.77]) (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 BD222970 for ; Thu, 4 May 2017 19:46:04 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 20629 invoked from network); 4 May 2017 19:40:33 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 4 May 2017 19:40:33 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.40.0) with SMTP; Thu, 04 May 2017 15:39:23 -0400 (EDT) Received: (qmail 26729 invoked from network); 4 May 2017 19:39:23 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 4 May 2017 19:39:23 -0000 Received: from [192.168.1.106] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id F13DDEC7C39; Thu, 4 May 2017 12:39:22 -0700 (PDT) From: Mark Millard Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: llvm FreeBSD powerpc ABI target bug fix: Re: [Bug 26519] Clang 4.0.0's "Target: powerpc-unknown-freebsd11.0" code generation is violating the SVR4 ABI (SEGV can result) Date: Thu, 4 May 2017 12:39:22 -0700 References: To: Dimitry Andric , FreeBSD Toolchain , FreeBSD PowerPC ML In-Reply-To: Message-Id: <0103401A-CEEA-4992-A45E-E60EA151119B@dsl-only.net> X-Mailer: Apple Mail (2.3273) 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, 04 May 2017 19:46:05 -0000 I just got a report of a fix for the FreeBSD powerpc ABI's code generation in llvm. It should fix a stack handling related problem that currently makes clang (through 4) largely useless for TARGET_ARCH=3Dpowerpc . On 2017-May-4, at 12:26 PM, bugzilla-daemon@llvm.org wrote: > Comment # 19 on bug 26519 from Krzysztof Parzyszek > Committed a fix in r302183. >=20 > You are receiving this mail because: > =E2=80=A2 You reported the bug. This would also apply to: powerpc-unknown-freebsd12.0 not just 11.0 Hopefully it is an easy merge into clang 4. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Thu May 4 19:48:11 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 CC264D5D4CD for ; Thu, 4 May 2017 19:48:11 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-77.reflexion.net [208.70.210.77]) (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 7A562A63 for ; Thu, 4 May 2017 19:48:10 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 16410 invoked from network); 4 May 2017 19:48:09 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 4 May 2017 19:48:09 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.40.0) with SMTP; Thu, 04 May 2017 15:48:09 -0400 (EDT) Received: (qmail 10908 invoked from network); 4 May 2017 19:48:09 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 4 May 2017 19:48:09 -0000 Received: from [192.168.1.106] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id BCFDFEC7C39; Thu, 4 May 2017 12:48:08 -0700 (PDT) From: Mark Millard Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: llvm FreeBSD powerpc ABI target bug fix: Re: [Bug 26519] Clang 4.0.0's "Target: powerpc-unknown-freebsd11.0" code generation is violating the SVR4 ABI (SEGV can result) Date: Thu, 4 May 2017 12:48:08 -0700 References: <0103401A-CEEA-4992-A45E-E60EA151119B@dsl-only.net> To: Dimitry Andric , FreeBSD Toolchain , FreeBSD PowerPC ML In-Reply-To: <0103401A-CEEA-4992-A45E-E60EA151119B@dsl-only.net> Message-Id: <83A99A4B-3F6A-437F-84C3-510359B303EE@dsl-only.net> X-Mailer: Apple Mail (2.3273) 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, 04 May 2017 19:48:11 -0000 On 2017-May-4, at 12:39 PM, Mark Millard wrote: > I just got a report of a fix for the FreeBSD > powerpc ABI's code generation in llvm. It should > fix a stack handling related problem that > currently makes clang (through 4) largely useless > for TARGET_ARCH=3Dpowerpc . >=20 > On 2017-May-4, at 12:26 PM, bugzilla-daemon@llvm.org wrote: >=20 >> Comment # 19 on bug 26519 from Krzysztof Parzyszek >> Committed a fix in r302183. >>=20 >> You are receiving this mail because: >> =E2=80=A2 You reported the bug. >=20 > This would also apply to: >=20 > powerpc-unknown-freebsd12.0 >=20 > not just 11.0 >=20 > Hopefully it is an easy merge into > clang 4. And another notice, this time indicating a request for an official merge to 4.0.1: Begin forwarded message: From: bugzilla-daemon at llvm.org Subject: [Bug 26519] Clang 4.0.0's "Target: powerpc-unknown-freebsd11.0" = code generation is violating the SVR4 ABI (SEGV can result) Date: May 4, 2017 at 12:42:26 PM PDT To: Krzysztof Parzyszek changed bug 26519=20 What Removed Added Status REOPENED RESOLVED Resolution --- FIXED Comment # 20 on bug 26519 from Krzysztof Parzyszek Opened PR32930 to request merging this into 4.0.1. You are receiving this mail because: =E2=80=A2 You reported the bug. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Thu May 4 21:42:04 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 3649DD5E5C3; Thu, 4 May 2017 21:42:04 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "tensor.andric.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EDB5281B; Thu, 4 May 2017 21:42:03 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from [IPv6:2001:470:7a58::4d79:8d91:26d1:3d20] (unknown [IPv6:2001:470:7a58:0:4d79:8d91:26d1:3d20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 12EF33AC59; Thu, 4 May 2017 23:41:55 +0200 (CEST) From: Dimitry Andric Message-Id: <893ECA11-7C80-4D24-A496-92ADC7978A07@FreeBSD.org> Content-Type: multipart/signed; boundary="Apple-Mail=_17DDA703-1B23-42AF-90DB-363455614ACF"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: llvm FreeBSD powerpc ABI target bug fix: Re: [Bug 26519] Clang 4.0.0's "Target: powerpc-unknown-freebsd11.0" code generation is violating the SVR4 ABI (SEGV can result) Date: Thu, 4 May 2017 23:41:39 +0200 In-Reply-To: <0103401A-CEEA-4992-A45E-E60EA151119B@dsl-only.net> Cc: FreeBSD Toolchain , FreeBSD PowerPC ML To: Mark Millard References: <0103401A-CEEA-4992-A45E-E60EA151119B@dsl-only.net> X-Mailer: Apple Mail (2.3273) 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, 04 May 2017 21:42:04 -0000 --Apple-Mail=_17DDA703-1B23-42AF-90DB-363455614ACF Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 On 4 May 2017, at 21:39, Mark Millard wrote: >=20 > I just got a report of a fix for the FreeBSD > powerpc ABI's code generation in llvm. It should > fix a stack handling related problem that > currently makes clang (through 4) largely useless > for TARGET_ARCH=3Dpowerpc . >=20 > On 2017-May-4, at 12:26 PM, bugzilla-daemon@llvm.org wrote: >=20 >> Comment # 19 on bug 26519 from Krzysztof Parzyszek >> Committed a fix in r302183. >>=20 >> You are receiving this mail because: >> =E2=80=A2 You reported the bug. >=20 > This would also apply to: >=20 > powerpc-unknown-freebsd12.0 >=20 > not just 11.0 >=20 > Hopefully it is an easy merge into > clang 4. Thanks for the notice. I have merged the upstream fix into head in r317810, and I will MFC it after a few days. -Dimitry --Apple-Mail=_17DDA703-1B23-42AF-90DB-363455614ACF Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.30 iEYEARECAAYFAlkLoCIACgkQsF6jCi4glqOCigCeJPAbPVmNQuzqFJMfnf/Bmw+k J9AAoPkJoGW36guBNq33FWsy7rpO50LZ =mbpM -----END PGP SIGNATURE----- --Apple-Mail=_17DDA703-1B23-42AF-90DB-363455614ACF-- From owner-freebsd-ppc@freebsd.org Fri May 5 07:45:38 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 6FDE2D5EDEB for ; Fri, 5 May 2017 07:45:38 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-77.reflexion.net [208.70.210.77]) (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 20CEB15C8 for ; Fri, 5 May 2017 07:45:37 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 22200 invoked from network); 5 May 2017 07:45:36 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 5 May 2017 07:45:36 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v8.40.0) with SMTP; Fri, 05 May 2017 03:45:36 -0400 (EDT) Received: (qmail 11305 invoked from network); 5 May 2017 07:45:36 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 5 May 2017 07:45:36 -0000 Received: from [192.168.1.106] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 7C729EC7ED9; Fri, 5 May 2017 00:45:35 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: llvm FreeBSD powerpc ABI target bug fix: Re: [Bug 26519] Clang 4.0.0's "Target: powerpc-unknown-freebsd11.0" code generation is violating the SVR4 ABI (SEGV can result) From: Mark Millard In-Reply-To: <893ECA11-7C80-4D24-A496-92ADC7978A07@FreeBSD.org> Date: Fri, 5 May 2017 00:45:34 -0700 Cc: Dimitry Andric , FreeBSD Toolchain Content-Transfer-Encoding: quoted-printable Message-Id: <8F708AD1-055E-41BD-BD92-6A87C5FBAA60@dsl-only.net> References: <0103401A-CEEA-4992-A45E-E60EA151119B@dsl-only.net> <893ECA11-7C80-4D24-A496-92ADC7978A07@FreeBSD.org> To: FreeBSD PowerPC ML X-Mailer: Apple Mail (2.3273) 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: Fri, 05 May 2017 07:45:38 -0000 On 2017-May-4, at 2:41 PM, Dimitry Andric wrote: > On 4 May 2017, at 21:39, Mark Millard wrote: >>=20 >> I just got a report of a fix for the FreeBSD >> powerpc ABI's code generation in llvm. It should >> fix a stack handling related problem that >> currently makes clang (through 4) largely useless >> for TARGET_ARCH=3Dpowerpc . >>=20 >> On 2017-May-4, at 12:26 PM, bugzilla-daemon@llvm.org wrote: >>=20 >>> Comment # 19 on bug 26519 from Krzysztof Parzyszek >>> Committed a fix in r302183. >>>=20 >>> You are receiving this mail because: >>> =E2=80=A2 You reported the bug. >>=20 >> This would also apply to: >>=20 >> powerpc-unknown-freebsd12.0 >>=20 >> not just 11.0 >>=20 >> Hopefully it is an easy merge into >> clang 4. >=20 > Thanks for the notice. I have merged the upstream fix into head in > r317810, and I will MFC it after a few days. I now have an old PowerMac running: # uname -paKU FreeBSD FBSDG4S 12.0-CURRENT FreeBSD 12.0-CURRENT r317820M powerpc = powerpc 1200030 1200030 where buildworld was via clang 4 (an amd64->powerpc cross build). Even the classic tiny program that previously showed C++ exception handling was broken and would crash the program now works when re-compiled and re-linked. Commands that were previous broken now work. (But my testing is nearly minimal at this point.) The kernel is from gcc421. I did try booting a kernel built by system-clang 4 and it got to: exec /sbin/init: error 13 and a later alignment exception at sf_buf_alloc+0x260 (Hand transcribed screen information.) This is the same as the last time that I tried such. The exception involved: exec_map_first_page kern_execve sys_execve start_init fork_exit fork_trampoline For the gcc 4.2.1 based kernel boot I have had one odd fatal kernel trap (0x903a64a, "unknown") where the lr showed 0x907f . It reported being stopped at: ffs_truncate+0x1080 It appears that "call doadump" worked but I've not looked at what was put in /var/crash/ . =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Fri May 5 08:23:01 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 86C50D5E86E for ; Fri, 5 May 2017 08:23:01 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-77.reflexion.net [208.70.210.77]) (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 39082A2D for ; Fri, 5 May 2017 08:23:00 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 3142 invoked from network); 5 May 2017 08:22:59 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 5 May 2017 08:22:59 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.40.0) with SMTP; Fri, 05 May 2017 04:22:59 -0400 (EDT) Received: (qmail 21919 invoked from network); 5 May 2017 08:22:58 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 5 May 2017 08:22:58 -0000 Received: from [192.168.1.106] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 4EE72EC7ED9; Fri, 5 May 2017 01:22:58 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: llvm FreeBSD powerpc ABI target bug fix: Re: [Bug 26519] Clang 4.0.0's "Target: powerpc-unknown-freebsd11.0" code generation is violating the SVR4 ABI (SEGV can result) From: Mark Millard In-Reply-To: <8F708AD1-055E-41BD-BD92-6A87C5FBAA60@dsl-only.net> Date: Fri, 5 May 2017 01:22:57 -0700 Cc: FreeBSD Toolchain , Dimitry Andric Content-Transfer-Encoding: quoted-printable Message-Id: <78CD5050-2B2B-4213-AF11-7EF744F608B2@dsl-only.net> References: <0103401A-CEEA-4992-A45E-E60EA151119B@dsl-only.net> <893ECA11-7C80-4D24-A496-92ADC7978A07@FreeBSD.org> <8F708AD1-055E-41BD-BD92-6A87C5FBAA60@dsl-only.net> To: FreeBSD PowerPC ML X-Mailer: Apple Mail (2.3273) 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: Fri, 05 May 2017 08:23:01 -0000 On 2017-May-5, at 12:45 AM, Mark Millard wrote: > On 2017-May-4, at 2:41 PM, Dimitry Andric wrote: >=20 >> . . . >> Thanks for the notice. I have merged the upstream fix into head in >> r317810, and I will MFC it after a few days. >=20 > I now have an old PowerMac running: >=20 > # uname -paKU > FreeBSD FBSDG4S 12.0-CURRENT FreeBSD 12.0-CURRENT r317820M powerpc = powerpc 1200030 1200030 >=20 > where buildworld was via clang 4 (an amd64->powerpc > cross build). Even the classic tiny program that > previously showed C++ exception handling was broken > and would crash the program now works when > re-compiled and re-linked. Commands that were > previous broken now work. >=20 > (But my testing is nearly minimal at this point.) >=20 > The kernel is from gcc421. >=20 >=20 >=20 > I did try booting a kernel built by system-clang 4 > and it got to: >=20 > exec /sbin/init: error 13 >=20 > and a later alignment exception at sf_buf_alloc+0x260 >=20 > (Hand transcribed screen information.) >=20 > This is the same as the last time that I tried > such. The exception involved: >=20 > exec_map_first_page > kern_execve > sys_execve > start_init > fork_exit > fork_trampoline >=20 >=20 >=20 > For the gcc 4.2.1 based kernel boot I have > had one odd fatal kernel trap (0x903a64a, > "unknown") where the lr showed 0x907f . It > reported being stopped at: >=20 > ffs_truncate+0x1080 >=20 > It appears that "call doadump" worked but > I've not looked at what was put in > /var/crash/ . If I leave the PowerMac idle running: # uname -paKU FreeBSD FBSDG4S 12.0-CURRENT FreeBSD 12.0-CURRENT r317820M powerpc = powerpc 1200030 1200030 it eventually gets the same ffs_truncate-tied fatal kernel trap, with the same odd lr and the like. So, while I cannot directly cause the problem at a specific time, the problem is repeatable. I did not build the kernel with a so-called "red-zone" to work around any stack-operation ordering problems that might still be around. But I do not know that such is involved here. It may be a while before I manage to get that much of an analysis done. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Fri May 5 10:38:03 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 A6862D5E79F for ; Fri, 5 May 2017 10:38:03 +0000 (UTC) (envelope-from secretaria@ampformosa.com.ar) Received: from ws122.host4g.com (ws122.host4g.com [190.210.9.102]) by mx1.freebsd.org (Postfix) with ESMTP id 6BBAF1C36 for ; Fri, 5 May 2017 10:38:03 +0000 (UTC) (envelope-from secretaria@ampformosa.com.ar) Received: from ws65.host4g.com (ws65.host4g.com [190.210.9.40]) by ws122.host4g.com (Postfix) with ESMTP id 6C188807CA8DC for ; Fri, 5 May 2017 07:38:09 -0300 (ART) Received: from [142.0.42.11] (unknown [142.0.42.11]) by ws65.host4g.com (Postfix) with ESMTPA id 58CA142A1795 for ; Fri, 5 May 2017 07:37:16 -0300 (ART) Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Description: Mail message body Subject: Request To: freebsd-ppc@freebsd.org From: "Sir. Paul Judge" Date: Fri, 05 May 2017 03:37:48 -0700 Reply-To: sirpaulrjudge@outlook.com 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: Fri, 05 May 2017 10:38:03 -0000 Hello, Good Day to you and I hope this message meet you well. I hope this mail meets you well. Before I proceed, I will like to introduce= my self for better understanding, My name is Sir. Paul R. Judge, Non Indep= ent Executive Director with Standard Bank Group in South East Asia,one of t= he biggest independent financial institution, I am contacting you because I= want you to assist me in receiving a deposit of one of our late client A C= hinese National who died in 2005. Before his death he has a deposit of (Twe= nty Two Million Seven Hundred and Twenty Eight Thousand Four Hundred and Fo= urteen United States Dollars)in our bank. Though I know that a transaction = of this magnitude will make any one apprehensive and worried, but I am assu= ring you that all will be well at the end of the day. On July 7, 2005, series of coordinated terrorist bomb blasts hit the London= Subways, resulting in the loss of more than 52 people and unfortunately ou= r late client was among the people that died on that fateful day while he w= as in United Kingdom for a business meeting, all efforts to contact his rel= atives/family representatives turned unsuccessful, I have made several inqu= iries to your embassy to locate any his extended relatives but has been uns= uccessful. After several unsuccessful attempts, I decided to trace his last= name over the internet, to see if I could locate any member of his family = hence I contacted you as you have thesame last name with our late client. His account where his deposit of (Twenty Two Million Seven Hundred and Twen= ty Eight Thousand Four Hundred and Fourteen United States Dollars)USD22,728= .414.00 is no longer active and inoperative. My bank will declare the accou= nt unserviceable and thereby send the funds to the bank treasury if I do no= t present anyone as family representative or relative to our late client. I= will seek your consent to present you as the relative or family representa= tive of our late client since you share the same last name with the our lat= e client so that the funds on the account can be paid to you then you and I= can share the money for investment purposes in your country. If you can handle this with me, I will want you to send me a reply with, (Y= OUR FULL NAMES: CONTACT ADDRESS: DATE OF BIRTH: OCCUPATION: MOBILE/HOME TE= LEPHONE NUMBER) to enable me submit to my bank immediately for the release = of the funds to you as his relative and family representative. Please I do not want any direct link between us, my official lines are not = secured as they are periodically monitored please observe this instruction = religiously, all legal documents and paper work will be released to you as = soon as I receive your response with the required information. Thank you and I hope to read from you, Kindly send me all details to: sirpaulrjudge@outlook.com Regards, Sir Paul R. Judge, Non Independent Executive Director, Standard Bank Group. South East Asia. From owner-freebsd-ppc@freebsd.org Fri May 5 12:00:17 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 6C5F8D5F165 for ; Fri, 5 May 2017 12:00:17 +0000 (UTC) (envelope-from secretaria.centrosalud@ampformosa.com.ar) Received: from ws122.host4g.com (ws122.host4g.com [190.210.9.102]) by mx1.freebsd.org (Postfix) with ESMTP id 85B4229B for ; Fri, 5 May 2017 12:00:16 +0000 (UTC) (envelope-from secretaria.centrosalud@ampformosa.com.ar) Received: from ws65.host4g.com (ws65.host4g.com [190.210.9.40]) by ws122.host4g.com (Postfix) with ESMTP id DFAFC993FD66F for ; Fri, 5 May 2017 08:59:56 -0300 (ART) Received: from [142.0.42.11] (unknown [142.0.42.11]) by ws65.host4g.com (Postfix) with ESMTPA id 8022F42A1795 for ; Fri, 5 May 2017 08:59:03 -0300 (ART) MIME-Version: 1.0 Subject: Google User To: freebsd-ppc@freebsd.org From: "Google Inc" Date: Fri, 05 May 2017 04:59:35 -0700 Reply-To: admin@gpawardteam.com Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Description: Mail message body 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: Fri, 05 May 2017 12:00:18 -0000 Dear Google User, We congratulate you for being selected as one of our winner on the ongoing = award promotion. Find attached document with more information regarding you= r winning. Congratulation, Sundar Pichai, Chief Executive Officer, Google Inc. From owner-freebsd-ppc@freebsd.org Sat May 6 01:11:14 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 532F4D5D34F for ; Sat, 6 May 2017 01:11:14 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-78.reflexion.net [208.70.210.78]) (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 03D95ADE for ; Sat, 6 May 2017 01:11:13 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 7193 invoked from network); 6 May 2017 01:12:22 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 6 May 2017 01:12:22 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.40.0) with SMTP; Fri, 05 May 2017 21:11:12 -0400 (EDT) Received: (qmail 20507 invoked from network); 6 May 2017 01:11:12 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 6 May 2017 01:11:12 -0000 Received: from [192.168.1.106] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id A4878EC885D; Fri, 5 May 2017 18:11:11 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: llvm FreeBSD powerpc ABI target bug fix: Re: [Bug 26519] Clang 4.0.0's "Target: powerpc-unknown-freebsd11.0" code generation is violating the SVR4 ABI (SEGV can result) From: Mark Millard In-Reply-To: <78CD5050-2B2B-4213-AF11-7EF744F608B2@dsl-only.net> Date: Fri, 5 May 2017 18:11:11 -0700 Cc: FreeBSD PowerPC ML , FreeBSD Toolchain Content-Transfer-Encoding: quoted-printable Message-Id: References: <0103401A-CEEA-4992-A45E-E60EA151119B@dsl-only.net> <893ECA11-7C80-4D24-A496-92ADC7978A07@FreeBSD.org> <8F708AD1-055E-41BD-BD92-6A87C5FBAA60@dsl-only.net> <78CD5050-2B2B-4213-AF11-7EF744F608B2@dsl-only.net> To: Dimitry Andric X-Mailer: Apple Mail (2.3273) 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, 06 May 2017 01:11:14 -0000 On 2017-May-5, at 1:22 AM, Mark Millard wrote: > On 2017-May-5, at 12:45 AM, Mark Millard = wrote: >=20 >> On 2017-May-4, at 2:41 PM, Dimitry Andric wrote: >>=20 >>> . . . >>> Thanks for the notice. I have merged the upstream fix into head in >>> r317810, and I will MFC it after a few days. >>=20 >> I now have an old PowerMac running: >>=20 >> # uname -paKU >> FreeBSD FBSDG4S 12.0-CURRENT FreeBSD 12.0-CURRENT r317820M powerpc = powerpc 1200030 1200030 >>=20 >> where buildworld was via clang 4 (an amd64->powerpc >> cross build). Even the classic tiny program that >> previously showed C++ exception handling was broken >> and would crash the program now works when >> re-compiled and re-linked. Commands that were >> previous broken now work. I messed up and accidentally installed the gcc 4.2.1 world that I had also built. This is why C++ exceptions appeared to be working for powerpc. Both TARGET_ARCH=3Dpowerpc and TARGET_ARCH=3Dpowerpc64 have C++ exceptions still messed up. >> (But my testing is nearly minimal at this point.) >>=20 >> The kernel is from gcc421. >>=20 >>=20 >>=20 >> I did try booting a kernel built by system-clang 4 >> and it got to: >>=20 >> exec /sbin/init: error 13 >>=20 >> and a later alignment exception at sf_buf_alloc+0x260 >>=20 >> (Hand transcribed screen information.) >>=20 >> This is the same as the last time that I tried >> such. The exception involved: >>=20 >> exec_map_first_page >> kern_execve >> sys_execve >> start_init >> fork_exit >> fork_trampoline >>=20 >>=20 >>=20 >> For the gcc 4.2.1 based kernel boot I have >> had one odd fatal kernel trap (0x903a64a, >> "unknown") where the lr showed 0x907f . It >> reported being stopped at: >>=20 >> ffs_truncate+0x1080 >>=20 >> It appears that "call doadump" worked but >> I've not looked at what was put in >> /var/crash/ . >=20 > If I leave the PowerMac idle running: >=20 > # uname -paKU > FreeBSD FBSDG4S 12.0-CURRENT FreeBSD 12.0-CURRENT r317820M powerpc = powerpc 1200030 1200030 >=20 > it eventually gets the same ffs_truncate-tied fatal > kernel trap, with the same odd lr and the like. >=20 > So, while I cannot directly cause the problem > at a specific time, the problem is repeatable. >=20 > I did not build the kernel with a so-called > "red-zone" to work around any stack-operation > ordering problems that might still be around. > But I do not know that such is involved here. > It may be a while before I manage to get that > much of an analysis done. The ffs_truncate issue is odd: A) It was gcc 4.2.1 based for both kernel and world. B) I built a gcc 4.2.1 based debug kernel and installed it but that does not get the problem. I sam trying the gcc 4.2.1 debug kernel with the system clang 4 world now and will later switch to the gcc 4.2.1 non-debug kernel to see what happens. But being a pure gcc 4.2.1 environment originally suggests that the ffs_truncate issue is not clang-toolchain related. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Sat May 6 05:13:16 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 539E5D603FA for ; Sat, 6 May 2017 05:13:16 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-78.reflexion.net [208.70.210.78]) (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 17C8FE58 for ; Sat, 6 May 2017 05:13:15 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 4537 invoked from network); 6 May 2017 05:13:14 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 6 May 2017 05:13:14 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v8.40.0) with SMTP; Sat, 06 May 2017 01:13:14 -0400 (EDT) Received: (qmail 6315 invoked from network); 6 May 2017 05:13:13 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 6 May 2017 05:13:13 -0000 Received: from [192.168.1.106] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 240A6EC7DD3; Fri, 5 May 2017 22:13:13 -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.3 \(3273\)) Subject: Re: llvm FreeBSD powerpc ABI target bug fix: Re: [Bug 26519] Clang 4.0.0's "Target: powerpc-unknown-freebsd11.0" code generation is violating the SVR4 ABI (SEGV can result) Date: Fri, 5 May 2017 22:13:12 -0700 References: <0103401A-CEEA-4992-A45E-E60EA151119B@dsl-only.net> <893ECA11-7C80-4D24-A496-92ADC7978A07@FreeBSD.org> <8F708AD1-055E-41BD-BD92-6A87C5FBAA60@dsl-only.net> <78CD5050-2B2B-4213-AF11-7EF744F608B2@dsl-only.net> To: FreeBSD Toolchain , FreeBSD PowerPC ML In-Reply-To: Message-Id: X-Mailer: Apple Mail (2.3273) 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, 06 May 2017 05:13:16 -0000 On 2017-May-5, at 6:11 PM, Mark Millard wrote: > On 2017-May-5, at 1:22 AM, Mark Millard wrote: >=20 >> On 2017-May-5, at 12:45 AM, Mark Millard = wrote: >>=20 >>> On 2017-May-4, at 2:41 PM, Dimitry Andric = wrote: >>>=20 >>>> . . . >>>> Thanks for the notice. I have merged the upstream fix into head in >>>> r317810, and I will MFC it after a few days. >>>=20 >>> I now have an old PowerMac running: >>>=20 >>> # uname -paKU >>> FreeBSD FBSDG4S 12.0-CURRENT FreeBSD 12.0-CURRENT r317820M powerpc = powerpc 1200030 1200030 >>>=20 >>> where buildworld was via clang 4 (an amd64->powerpc >>> cross build). Even the classic tiny program that >>> previously showed C++ exception handling was broken >>> and would crash the program now works when >>> re-compiled and re-linked. Commands that were >>> previous broken now work. >=20 > I messed up and accidentally installed the > gcc 4.2.1 world that I had also built. This > is why C++ exceptions appeared to be working > for powerpc. >=20 > Both TARGET_ARCH=3Dpowerpc and TARGET_ARCH=3Dpowerpc64 > have C++ exceptions still messed up. >=20 >=20 >>> . . . >>>=20 >>> For the gcc 4.2.1 based kernel boot I have >>> had one odd fatal kernel trap (0x903a64a, >>> "unknown") where the lr showed 0x907f . It >>> reported being stopped at: >>>=20 >>> ffs_truncate+0x1080 >>>=20 >>> It appears that "call doadump" worked but >>> I've not looked at what was put in >>> /var/crash/ . >>=20 >> If I leave the PowerMac idle running: >>=20 >> # uname -paKU >> FreeBSD FBSDG4S 12.0-CURRENT FreeBSD 12.0-CURRENT r317820M powerpc = powerpc 1200030 1200030 >>=20 >> it eventually gets the same ffs_truncate-tied fatal >> kernel trap, with the same odd lr and the like. >>=20 >> So, while I cannot directly cause the problem >> at a specific time, the problem is repeatable. >>=20 >> I did not build the kernel with a so-called >> "red-zone" to work around any stack-operation >> ordering problems that might still be around. >> But I do not know that such is involved here. >> It may be a while before I manage to get that >> much of an analysis done. >=20 > The ffs_truncate issue is odd: >=20 > A) It was gcc 4.2.1 based for both kernel and world. > B) I built a gcc 4.2.1 based debug kernel and > installed it but that does not get the problem. >=20 > I sam trying the gcc 4.2.1 debug kernel with the > system clang 4 world now and will later switch > to the gcc 4.2.1 non-debug kernel to see what > happens. >=20 > But being a pure gcc 4.2.1 environment originally > suggests that the ffs_truncate issue is not > clang-toolchain related. I found a bad (old) kernel module in /boot/kernel/ and eliminating it appears to have removed the ffs_truncate problem. And even more good news: buildworld buildkernel makes extensive use of signals and its failure is how I discovered the original stack handling problems for powerpc (the ABI violations). I used to have to patch in so-called "red zone" handling to avoid the issue. No more: a running a kernel that was built without a "red zone" and running a world based on clang now allows buildworld buildkernel to complete just fine: no evidence of ABI violations in the world code that is executed. Going the other direction: I've conformed that clang still generates C++ programs that can not handle thrown exceptions. Both powerpc and powerpc64 are this way. The only other area with an issue that I know of is the exec /sbin/init failure that prevents using the clang based kernel for powerpc. (This is based on the system binutils for powerpc and devel/*binutils for powerpc64 instead of lld and such. lld has its own problems for these targets.) I already build and run powerpc64 kernels built by clang. That has been true for a while. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Sat May 6 07:06: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 D1847D600EF for ; Sat, 6 May 2017 07:06:15 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-77.reflexion.net [208.70.210.77]) (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 731C51500 for ; Sat, 6 May 2017 07:06:14 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 10791 invoked from network); 6 May 2017 07:07:18 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 6 May 2017 07:07:18 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.40.0) with SMTP; Sat, 06 May 2017 03:06:07 -0400 (EDT) Received: (qmail 7540 invoked from network); 6 May 2017 07:06:07 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 6 May 2017 07:06:07 -0000 Received: from [192.168.1.106] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 0C1FDEC7ED9; Sat, 6 May 2017 00:06:07 -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.3 \(3273\)) Subject: Re: llvm FreeBSD powerpc ABI target bug fix: Re: [Bug 26519] Clang 4.0.0's "Target: powerpc-unknown-freebsd11.0" code generation is violating the SVR4 ABI (SEGV can result) Date: Sat, 6 May 2017 00:06:06 -0700 References: <0103401A-CEEA-4992-A45E-E60EA151119B@dsl-only.net> <893ECA11-7C80-4D24-A496-92ADC7978A07@FreeBSD.org> <8F708AD1-055E-41BD-BD92-6A87C5FBAA60@dsl-only.net> <78CD5050-2B2B-4213-AF11-7EF744F608B2@dsl-only.net> To: FreeBSD Toolchain , FreeBSD PowerPC ML In-Reply-To: Message-Id: X-Mailer: Apple Mail (2.3273) 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, 06 May 2017 07:06:16 -0000 On 2017-May-5, at 10:13 PM, Mark Millard wrote: > On 2017-May-5, at 6:11 PM, Mark Millard wrote: >=20 >>>> . . . >>>>=20 >>>> For the gcc 4.2.1 based kernel boot I have >>>> had one odd fatal kernel trap (0x903a64a, >>>> "unknown") where the lr showed 0x907f . It >>>> reported being stopped at: >>>>=20 >>>> ffs_truncate+0x1080 >>>>=20 >>>> It appears that "call doadump" worked but >>>> I've not looked at what was put in >>>> /var/crash/ . >>>=20 >>> If I leave the PowerMac idle running: It also happens when busy. >>> # uname -paKU >>> FreeBSD FBSDG4S 12.0-CURRENT FreeBSD 12.0-CURRENT r317820M powerpc = powerpc 1200030 1200030 >>>=20 >>> it eventually gets the same ffs_truncate-tied fatal >>> kernel trap, with the same odd lr and the like. >>>=20 >>> So, while I cannot directly cause the problem >>> at a specific time, the problem is repeatable. >>>=20 >>> . . . >>=20 >> The ffs_truncate issue is odd: >>=20 >> A) It was gcc 4.2.1 based for both kernel and world. >> B) I built a gcc 4.2.1 based debug kernel and >> installed it but that does not get the problem. >>=20 >> I sam trying the gcc 4.2.1 debug kernel with the >> system clang 4 world now and will later switch >> to the gcc 4.2.1 non-debug kernel to see what >> happens. >>=20 >> But being a pure gcc 4.2.1 environment originally >> suggests that the ffs_truncate issue is not >> clang-toolchain related. >=20 > I found a bad (old) kernel module in /boot/kernel/ > and eliminating it appears to have removed the > ffs_truncate problem. >=20 > . . . For the ffs_truncate problem I spoke too soon: It happened again, this time while the old PowerMac was busy. The detail numbers and such were again the same. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Sat May 6 09:59:43 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 A0F6CD5D7F4 for ; Sat, 6 May 2017 09:59:43 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-77.reflexion.net [208.70.210.77]) (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 4A605D79 for ; Sat, 6 May 2017 09:59:42 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 18798 invoked from network); 6 May 2017 09:59:40 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 6 May 2017 09:59:40 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.40.0) with SMTP; Sat, 06 May 2017 05:59:40 -0400 (EDT) Received: (qmail 25212 invoked from network); 6 May 2017 09:59:40 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 6 May 2017 09:59:40 -0000 Received: from [192.168.1.106] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id A2B16EC7DD3; Sat, 6 May 2017 02:59:39 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: llvm FreeBSD powerpc ABI target bug fix: Re: [Bug 26519] Clang 4.0.0's "Target: powerpc-unknown-freebsd11.0" code generation is violating the SVR4 ABI (SEGV can result) From: Mark Millard In-Reply-To: Date: Sat, 6 May 2017 02:59:39 -0700 Cc: Dimitry Andric Content-Transfer-Encoding: quoted-printable Message-Id: <528DD22A-D880-4BA1-8FA8-BB9CC5004434@dsl-only.net> References: <0103401A-CEEA-4992-A45E-E60EA151119B@dsl-only.net> <893ECA11-7C80-4D24-A496-92ADC7978A07@FreeBSD.org> <8F708AD1-055E-41BD-BD92-6A87C5FBAA60@dsl-only.net> <78CD5050-2B2B-4213-AF11-7EF744F608B2@dsl-only.net> To: FreeBSD Toolchain , FreeBSD PowerPC ML X-Mailer: Apple Mail (2.3273) 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, 06 May 2017 09:59:43 -0000 [I'm top posting a find of another stack handling failure example from the updated compiler for TARGET_ARCH=3Dpowerpc .] Bad news: Another code generation error, this time demonstrated in compiling part of perl5. . . (I tried to build a port that indirectly tried build perl5 but perl5's miniperl crashes.) /usr/obj/portswork/usr/ports/lang/perl5.24/work/perl-5.24.1/numeric.c has Perl_cast_iv(NV f) for which clang double stores two different things to one address [24(r1)]. Below the =3D> lines are the double store, the second destroying the r30 value that was saved in the first: Dump of assembler code for function Perl_cast_iv: 0x0196a114 <+0>: mflr r0 0x0196a118 <+4>: stw r0,4(r1) 0x0196a11c <+8>: stwu r1,-32(r1) 0x0196a120 <+12>: stw r31,28(r1) =3D> 0x0196a124 <+16>: stw r30,24(r1) 0x0196a128 <+20>: mr r31,r1 0x0196a12c <+24>: mfcr r12 =3D> 0x0196a130 <+28>: stw r12,24(r31) Note: r31 =3D=3D r1 for that second "=3D>" line. The return code sequence has a similar problem: two loads from the same address for what should be distinct values. Note: r31 =3D=3D r1 here too. =3D> 0x0196a1bc <+168>: lwz r12,24(r31) 0x0196a1c0 <+172>: lwz r0,36(r1) 0x0196a1c4 <+176>: lwz r31,28(r1) =3D> 0x0196a1c8 <+180>: lwz r30,24(r1) 0x0196a1cc <+184>: mtcrf 32,r12 0x0196a1d0 <+188>: addi r1,r1,32 0x0196a1d4 <+192>: mtlr r0 0x0196a1d8 <+196>: blr The Perl_cast_iv source code looks like: IV Perl_cast_iv(NV f) { if (f < IV_MAX_P1) return f < IV_MIN ? IV_MIN : (IV) f; if (f < UV_MAX_P1) { #if CASTFLAGS & 2 /* For future flexibility allowing for sizeof(UV) >=3D sizeof(IV) = */ if (f < UV_MAX_P1_HALF) return (IV)(UV) f; f -=3D UV_MAX_P1_HALF; return (IV)(((UV) f) | (1 + (UV_MAX >> 1))); #else return (IV)(UV) f; #endif } return f > 0 ? (IV)UV_MAX : 0 /* NaN */; } This sort of thing might explain the occasional panic that names ffs_truncate if there is some infrequently used routine that messes up the stack. On 2017-May-6, at 12:06 AM, Mark Millard wrote: > On 2017-May-5, at 10:13 PM, Mark Millard = wrote: >=20 >=20 >> On 2017-May-5, at 6:11 PM, Mark Millard = wrote: >>=20 >>>>> . . . >>>>>=20 >>>>> For the gcc 4.2.1 based kernel boot I have >>>>> had one odd fatal kernel trap (0x903a64a, >>>>> "unknown") where the lr showed 0x907f . It >>>>> reported being stopped at: >>>>>=20 >>>>> ffs_truncate+0x1080 >>>>>=20 >>>>> It appears that "call doadump" worked but >>>>> I've not looked at what was put in >>>>> /var/crash/ . >>>>=20 >>>> If I leave the PowerMac idle running: >=20 > It also happens when busy. >=20 >>>> # uname -paKU >>>> FreeBSD FBSDG4S 12.0-CURRENT FreeBSD 12.0-CURRENT r317820M = powerpc powerpc 1200030 1200030 >>>>=20 >>>> it eventually gets the same ffs_truncate-tied fatal >>>> kernel trap, with the same odd lr and the like. >>>>=20 >>>> So, while I cannot directly cause the problem >>>> at a specific time, the problem is repeatable. >>>>=20 >>>> . . . >>>=20 >>> The ffs_truncate issue is odd: >>>=20 >>> A) It was gcc 4.2.1 based for both kernel and world. >>> B) I built a gcc 4.2.1 based debug kernel and >>> installed it but that does not get the problem. >>>=20 >>> I sam trying the gcc 4.2.1 debug kernel with the >>> system clang 4 world now and will later switch >>> to the gcc 4.2.1 non-debug kernel to see what >>> happens. >>>=20 >>> But being a pure gcc 4.2.1 environment originally >>> suggests that the ffs_truncate issue is not >>> clang-toolchain related. >>=20 >> I found a bad (old) kernel module in /boot/kernel/ >> and eliminating it appears to have removed the >> ffs_truncate problem. >>=20 >> . . . >=20 > For the ffs_truncate problem I spoke too > soon: It happened again, this time while > the old PowerMac was busy. >=20 > The detail numbers and such were again the > same. =3D=3D=3D Mark Millard markmi at dsl-only.net