[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-282601-105":53,"doc-detail-282601-en":126},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":119,"head_meta":121,"extra_data":123,"updated_unix":125},105,"en","khronos-group-request-for-proposals-llvm-spir-v-backend-re-issued-with-clarifications-may-2025","Khronos Group Request for Proposals - LLVM SPIR-V Backend - Re-issued with Clarifications May 2025","","Khronos Group issues a Request for Proposals focused on aligning the experimental LLVM SPIR-V Backend with the capabilities of the Khronos LLVM/SPIR-V Bi-Directional Translator. The work targets functional parity by porting and extending LLVM Integrated Testing (LIT) coverage, implementing and validating missing LLVM intrinsic lowering, and adding or correcting SPIR-V extensions. Coordination uses public LLVM and Khronos repositories, with status updates for OpenCL and SPIR-V working groups.",{"@graph":63,"@context":118},[64,80,101],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":51,"@type":70,"position":76},"https://docshare.wps.com/template/general/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/khronos-group-request-for-proposals-llvm-spir-v-backend-re-issued-with-clarifications-may-2025/282601/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/khronos-group-request-for-proposals-llvm-spir-v-backend-re-issued-with-clarifications-may-2025/282601.png","ImageObject",442,249,{"name":88,"@type":89},"Hazel","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-09-21","2026-09-16",true,{"@type":98,"interactionType":99,"userInteractionCount":76},"InteractionCounter",{"@type":100},"ViewAction",{"@type":102,"mainEntity":103},"FAQPage",[104,110,114],{"name":105,"@type":106,"acceptedAnswer":107},"What is the main objective of this RFP?","Question",{"text":108,"@type":109},"To align the LLVM SPIR-V Backend’s capabilities with those supported by the Khronos LLVM/SPIR-V Bi-Directional Translator by addressing missing or incomplete functionalities.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"Which work areas are included in the project scope?",{"text":113,"@type":109},"Porting existing LIT tests (excluding DWARF reverse-translation cases), implementing and testing missing LLVM intrinsic lowering, implementing and testing missing SPIR-V extensions, and optionally adding missing OpenCL builtin TableGen definitions when they affect the prior items.",{"name":115,"@type":106,"acceptedAnswer":116},"How will respondents coordinate and where will code changes be made?",{"text":117,"@type":109},"Project communications will use a Khronos Slack channel, and code development will occur in the public LLVM project repository and the Khronos translator repository via GitHub pull requests and issues reviewed by OpenCL and SPIR working group members.","https://schema.org",{"og:url":78,"og:type":120,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":122,"canonical":78},"index,follow",{"doc_id":124,"site_id":56},282601,1789578105,{"code":4,"msg":5,"data":127},{"doc_id":124,"user_id":128,"nickname":88,"user_avatar":129,"doc_module":9,"category_id":50,"category_name":51,"doc_title":59,"doc_description":61,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":76,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":47,"language":135,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":136,"faqs":137,"seo_title":138,"seo_description":61,"update_tm":125,"read_time":73},137441390410,"https://ap-avatar.wpscdn.com/avatar/2000252f4ab5702993?_k=1776741390130283984","Khronos Group Request for Proposals  \nLLVM SPIR-V Backend  \nNovember 2024  \nRe-issued with Clarifications May 2025  \nNotice  \nALL KHRONOS® SPECIFICATIONS AND OTHER DOCUMENTS (TOGETHER AND SEPARATELY, “MATERIALS”) IN ASSOCIATION WITH THIS RFP ARE BEING PROVIDED “AS IS.” KHRONOS MAKES NO WARRANTIES, EXPRESSED, IMPLIED, STATUTORY OR OTHERWISE WITH RESPECT TO THE MATERIALS, AND EXPRESSLY DISCLAIMS ALL IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  \nAny information furnished is believed to be accurate and reliable. However, Khronos assumes no responsibility for the consequences of use of such information or for any infringement of patents or other rights of third parties that may result from its use. No license is granted by implication or otherwise under any patent or patent rights of Khronos. Specifications mentioned in this publication are subject to change without notice. This publication supersedes and replaces all information previously supplied.  \nTrademarks  \nKhronos®, SPIR® and SPIR-V™, and associated logos, are trademarks or registered trademarks of Khronos Group Inc. All other product names, trademarks, and/or company names are used solely for identification and belong to their respective owners.  \n1. Background  \nThe SPIR-V target within LLVM, also known as the LLVM SPIR-V Backend, facilitates code generation for the OpenCL SPIR-V binary format, as outlined in the SPIR-V specification [1] . This Backend was upstreamed into the LLVM repository in 2022 and is on track to become a stable, permanent target. Historically, the Khronos LLVM/SPIR-V Bi-Directional Translator has served as the official tool for generating SPIR-V from LLVM IR. However, due to ongoing developments and contributions from various SPIR-V vendors, the Backend is anticipated to fully supplant the Translator.  \nThe goal of this project is to address and integrate specific functionalities that are currently available in the Translator project but missing from the Backend.  \n2. Methodology  \nKhronos has a fixed budget for this project, with payment due on project completion.  \nThis RFP is being circulated to all Khronos members, and publicly, any interested party is welcome to respond.  \nA Khronos Slack channel will be used for project communications that any interested Khronos member may join. Short status and progress reports should be prepared for the weekly OpenCL and SPIR-V Working Group meetings, and the biweekly OpenCL Tooling meetings and circulated on the email lists for those groups.  \nAll code development shall take in place in the public LLVM project repository [3], and the Khronos LLVM/SPIR-V Bi-Directional Translator repository [4], using GitHub pull requests and issues reviewed by OpenCL and SPIR Working Group members.  \n3. Scope  \n3.1 Work Areas  \nThe scope of this Request for Proposals (RFP) is concentrated on aligning the capabilities of the experimental LLVM SPIR-V Backend with those currently supported by the Khronos LLVM/SPIR-V Bi-Directional Translator. This involves several areas of work, some involving the LLVM’s Integrated Testing ( LIT) framework, outlined below in priority order:  \n1. Port existing tests: port existing LIT tests from the Translator to test the Backend and contribute current Backend L ITs back to the Khronos repository. This will help identify future areas of work to ensure functional parity. This excludes any DWARF test cases since LLVM does not support “reverse translation”from SPIR-V to LLVM IR.  \n2. Implement and test LLVM intrinsics lowering methods: implement and test missing intrinsics, and correct current implementations, by running existing LIT and Translator tests or creating new tests as necessary. Any created tests shall be contributed back to the Khronos repository.  \n3. Implement and test SPIR-V extensions: implement and test missing SPIR-V extensions, and correct current implementations, by running existing LIT and Translator tests or creating new test","cbCaicuqMpuaBe58","https://ap.wps.com/l/cbCaicuqMpuaBe58","pdf",283646,"English","# Background\n# Methodology\n# Scope\n## Work Areas\n## Priority Intrinsics and Extensions\n## Clarifications","[{\"question\":\"What is the main objective of this RFP?\",\"answer\":\"To align the LLVM SPIR-V Backend’s capabilities with those supported by the Khronos LLVM/SPIR-V Bi-Directional Translator by addressing missing or incomplete functionalities.\"},{\"question\":\"Which work areas are included in the project scope?\",\"answer\":\"Porting existing LIT tests (excluding DWARF reverse-translation cases), implementing and testing missing LLVM intrinsic lowering, implementing and testing missing SPIR-V extensions, and optionally adding missing OpenCL builtin TableGen definitions when they affect the prior items.\"},{\"question\":\"How will respondents coordinate and where will code changes be made?\",\"answer\":\"Project communications will use a Khronos Slack channel, and code development will occur in the public LLVM project repository and the Khronos translator repository via GitHub pull requests and issues reviewed by OpenCL and SPIR working group members.\"}]","Khronos Group Request for Proposals - LLVM SPIR-V Backend - Re-issued with Clarifications May 2025 | PDF"]