Auto merge of #164455 - sgasho:offload-cleanup-1, r=ZuseZ4 offload: remove device.bin and pass device bitcode directly related: https://github.com/rust-lang/rust/issues/164057 Since rust-lang/rust#162309 removed the `clang-linker-wrapper` step, nothing reads `device.bin` anymore, and its triple/arch are already in the bitcode. So, as the first step, I removed steps generating and extracting device.bin, instead we're going to use the device bitcode. As a next step, the host pass could take the linked device output(`.ptx` for NVPTX, `.elf` for AMDGPU) instead, which would remove the second codegen. I'd like to do that in a separate PR. I'll update rustc-dev-guide in a follow-up PR in their repo. I verified that this change works by running offload sample code on UofT gpunode. r? ZuseZ4
Website | Getting started | Learn | Documentation | Contributing
This is the main source code repository for Rust. It contains the compiler, standard library, and documentation.
Performance: Fast and memory-efficient, suitable for critical services, embedded devices, and easily integrated with other languages.
Reliability: Our rich type system and ownership model ensure memory and thread safety, reducing bugs at compile-time.
Productivity: Comprehensive documentation, a compiler committed to providing great diagnostics, and advanced tooling including package manager and build tool (Cargo), auto-formatter (rustfmt), linter (Clippy) and editor support (rust-analyzer).
Read “Installation” from The Book.
If you really want to install from source (though this is not recommended), see INSTALL.md.
See https://www.rust-lang.org/community for a list of chat platforms and forums.
See CONTRIBUTING.md.
For a detailed explanation of the compiler's architecture and how to begin contributing, see the rustc-dev-guide.
Rust is primarily distributed under the terms of both the MIT license and the Apache License (Version 2.0), with portions covered by various BSD-like licenses.
See LICENSE-APACHE, LICENSE-MIT, and COPYRIGHT for details.
The Rust Foundation owns and protects the Rust and Cargo trademarks and logos (the “Rust Trademarks”).
If you want to use these names or brands, please read the Rust language trademark policy.
Third-party logos may be subject to third-party copyrights and trademarks. See Licenses for details.