{"title":"安全关键系统的SYCL新功能","authors":"Erik Tomusk, Verena Beckham","doi":"10.1145/3585341.3585367","DOIUrl":null,"url":null,"abstract":"In April 2022, Codeplay and CoreAVI initiated the SYCL SC Exploratory Forum within Khronos to evaluate industry interest in a new Khronos API based on SYCL and targeted at safety-critical industries[1]. A year later, we take stock of the progress the Exploratory Forum has made on defining SYCL for Safety-Critical Systems, and we share some of the insights we have gained. Safety-critical industries, like avionics, automotive, nuclear, and rail, require their software to be compliant to safety standards such as ISO 26262, ISO 21448/SOTIF, DO-178C, and UL4600, as well as to adhere to guidelines such as those defined by AUTOSAR and MISRA. While safety-critical industries have traditionally been cautious about adopting new or unproven technologies, interest by these industries in C++ and heterogeneous programming has increased significantly in recent years. This is driven, in large part, by the need for AI technologies to implement advanced features, such as autonomous behavior. Compute-heavy workloads like AI require high-level programming frameworks as well as considerable computing power, which can only be achieved by a heterogeneous system design. SYCL’s single-source C++ programming model has already become popular in the HPC industry. The proposed SYCL for Safety-Critical Systems API aims to open up high-level heterogeneous compute to safety-critical industries by introducing modifications and extensions to SYCL to make both SYCL applications and SYCL implementations easier to certify to industry safety standards. In this talk, we will give an overview of what certification to a safety standard implies for a compiler and runtime based on SYCL. Khronos Exploratory Forums are designed to be open to companies and individuals who are not yet Khronos participants. A key aim of the SYCL SC Exploratory Forum was to hear from “end-user” companies in safety-critical domains, and to evaluate the market for a safety-critical API based on SYCL. The talk will give an overview of the companies that participated and their general feedback. In the initial phase, the SYCL SC Exploratory Forum heard presentations from its participants and collated a “wish list” of features for a high-level heterogeneous compute API. The talk will give an overview of features that were requested and a discussion of some of the more interesting points. In the second stage, the members of the Forum analyzed these “wishes” according to their relevance to a safety-critical standard specifically based on SYCL. A list of core requirements for the SYCL for Safety-Critical Systems API was distilled from the wish list and will act as a guide during the definition of the new standard. The talk will include an overview of the requirements, background on the finer technical points, and some of the technical discussions that were had around these topics. The presentation will also describe some of the open questions that are still to be answered during the design of the SYCL for Safety-Critical Systems API. The presentation will close with a call to join the discussions and help define the details of this new standard, which promises to open up the SYCL programming model to safety-critical industries.","PeriodicalId":360830,"journal":{"name":"Proceedings of the 2023 International Workshop on OpenCL","volume":"14 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2023-04-18","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":"{\"title\":\"What’s New in SYCL for Safety Critical Systems\",\"authors\":\"Erik Tomusk, Verena Beckham\",\"doi\":\"10.1145/3585341.3585367\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"In April 2022, Codeplay and CoreAVI initiated the SYCL SC Exploratory Forum within Khronos to evaluate industry interest in a new Khronos API based on SYCL and targeted at safety-critical industries[1]. A year later, we take stock of the progress the Exploratory Forum has made on defining SYCL for Safety-Critical Systems, and we share some of the insights we have gained. Safety-critical industries, like avionics, automotive, nuclear, and rail, require their software to be compliant to safety standards such as ISO 26262, ISO 21448/SOTIF, DO-178C, and UL4600, as well as to adhere to guidelines such as those defined by AUTOSAR and MISRA. While safety-critical industries have traditionally been cautious about adopting new or unproven technologies, interest by these industries in C++ and heterogeneous programming has increased significantly in recent years. This is driven, in large part, by the need for AI technologies to implement advanced features, such as autonomous behavior. Compute-heavy workloads like AI require high-level programming frameworks as well as considerable computing power, which can only be achieved by a heterogeneous system design. SYCL’s single-source C++ programming model has already become popular in the HPC industry. The proposed SYCL for Safety-Critical Systems API aims to open up high-level heterogeneous compute to safety-critical industries by introducing modifications and extensions to SYCL to make both SYCL applications and SYCL implementations easier to certify to industry safety standards. In this talk, we will give an overview of what certification to a safety standard implies for a compiler and runtime based on SYCL. Khronos Exploratory Forums are designed to be open to companies and individuals who are not yet Khronos participants. A key aim of the SYCL SC Exploratory Forum was to hear from “end-user” companies in safety-critical domains, and to evaluate the market for a safety-critical API based on SYCL. The talk will give an overview of the companies that participated and their general feedback. In the initial phase, the SYCL SC Exploratory Forum heard presentations from its participants and collated a “wish list” of features for a high-level heterogeneous compute API. The talk will give an overview of features that were requested and a discussion of some of the more interesting points. In the second stage, the members of the Forum analyzed these “wishes” according to their relevance to a safety-critical standard specifically based on SYCL. A list of core requirements for the SYCL for Safety-Critical Systems API was distilled from the wish list and will act as a guide during the definition of the new standard. The talk will include an overview of the requirements, background on the finer technical points, and some of the technical discussions that were had around these topics. The presentation will also describe some of the open questions that are still to be answered during the design of the SYCL for Safety-Critical Systems API. The presentation will close with a call to join the discussions and help define the details of this new standard, which promises to open up the SYCL programming model to safety-critical industries.\",\"PeriodicalId\":360830,\"journal\":{\"name\":\"Proceedings of the 2023 International Workshop on OpenCL\",\"volume\":\"14 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2023-04-18\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"0\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"Proceedings of the 2023 International Workshop on OpenCL\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1145/3585341.3585367\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"Proceedings of the 2023 International Workshop on OpenCL","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1145/3585341.3585367","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 0
摘要
2022年4月,Codeplay和CoreAVI在Khronos内部发起了SYCL SC探索性论坛,以评估行业对基于SYCL的新Khronos API的兴趣,并针对安全关键行业b[1]。一年后,我们总结了探索性论坛在定义安全关键系统的SYCL方面取得的进展,并分享了我们获得的一些见解。安全关键行业,如航空电子、汽车、核能和铁路,要求他们的软件符合ISO 26262、ISO 21448/SOTIF、DO-178C和UL4600等安全标准,并遵守AUTOSAR和MISRA定义的指导方针。虽然安全关键行业传统上对采用新的或未经验证的技术持谨慎态度,但近年来,这些行业对c++和异构编程的兴趣显著增加。这在很大程度上是由人工智能技术实现高级功能(如自主行为)的需求驱动的。像AI这样的计算繁重的工作负载需要高级编程框架以及相当大的计算能力,这只能通过异构系统设计来实现。SYCL的单源c++编程模型已经在HPC行业中流行起来。提议的SYCL安全关键系统API旨在通过对SYCL进行修改和扩展,使SYCL应用程序和SYCL实现更容易通过行业安全标准认证,从而向安全关键行业开放高级异构计算。在这次演讲中,我们将概述安全标准认证对于基于SYCL的编译器和运行时意味着什么。Khronos探索性论坛旨在向尚未成为Khronos参与者的公司和个人开放。SYCL SC探索性论坛的一个主要目的是听取安全关键领域的“最终用户”公司的意见,并评估基于SYCL的安全关键API的市场。讲座将概述参与的公司以及他们的总体反馈。在初始阶段,SYCL SC探索性论坛听取了参与者的演讲,并整理了一个高级异构计算API的“愿望清单”。该演讲将概述所要求的功能,并讨论一些更有趣的点。在第二阶段,论坛成员根据这些“愿望”与具体基于SYCL的安全关键标准的相关性来分析这些“愿望”。安全关键系统API的SYCL核心需求列表是从愿望列表中提炼出来的,将作为新标准定义过程中的指南。该演讲将包括需求概述、详细技术要点的背景以及围绕这些主题进行的一些技术讨论。该演讲还将描述在SYCL for Safety-Critical Systems API的设计过程中仍然需要回答的一些开放问题。演讲结束时,将呼吁大家加入讨论,并帮助定义这个新标准的细节,该标准承诺向安全关键行业开放SYCL编程模型。
In April 2022, Codeplay and CoreAVI initiated the SYCL SC Exploratory Forum within Khronos to evaluate industry interest in a new Khronos API based on SYCL and targeted at safety-critical industries[1]. A year later, we take stock of the progress the Exploratory Forum has made on defining SYCL for Safety-Critical Systems, and we share some of the insights we have gained. Safety-critical industries, like avionics, automotive, nuclear, and rail, require their software to be compliant to safety standards such as ISO 26262, ISO 21448/SOTIF, DO-178C, and UL4600, as well as to adhere to guidelines such as those defined by AUTOSAR and MISRA. While safety-critical industries have traditionally been cautious about adopting new or unproven technologies, interest by these industries in C++ and heterogeneous programming has increased significantly in recent years. This is driven, in large part, by the need for AI technologies to implement advanced features, such as autonomous behavior. Compute-heavy workloads like AI require high-level programming frameworks as well as considerable computing power, which can only be achieved by a heterogeneous system design. SYCL’s single-source C++ programming model has already become popular in the HPC industry. The proposed SYCL for Safety-Critical Systems API aims to open up high-level heterogeneous compute to safety-critical industries by introducing modifications and extensions to SYCL to make both SYCL applications and SYCL implementations easier to certify to industry safety standards. In this talk, we will give an overview of what certification to a safety standard implies for a compiler and runtime based on SYCL. Khronos Exploratory Forums are designed to be open to companies and individuals who are not yet Khronos participants. A key aim of the SYCL SC Exploratory Forum was to hear from “end-user” companies in safety-critical domains, and to evaluate the market for a safety-critical API based on SYCL. The talk will give an overview of the companies that participated and their general feedback. In the initial phase, the SYCL SC Exploratory Forum heard presentations from its participants and collated a “wish list” of features for a high-level heterogeneous compute API. The talk will give an overview of features that were requested and a discussion of some of the more interesting points. In the second stage, the members of the Forum analyzed these “wishes” according to their relevance to a safety-critical standard specifically based on SYCL. A list of core requirements for the SYCL for Safety-Critical Systems API was distilled from the wish list and will act as a guide during the definition of the new standard. The talk will include an overview of the requirements, background on the finer technical points, and some of the technical discussions that were had around these topics. The presentation will also describe some of the open questions that are still to be answered during the design of the SYCL for Safety-Critical Systems API. The presentation will close with a call to join the discussions and help define the details of this new standard, which promises to open up the SYCL programming model to safety-critical industries.