rust/compiler/rustc_codegen_llvm/src/llvm, branch tryhttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=try2025-07-21T16:54:24+00:00Rollup merge of #142097 - ZuseZ4:offload-host1, r=oli-obk2025-07-21T16:54:24+00:00许杰友 Jieyou Xu (Joe)39484203+jieyouxu@users.noreply.github.com2025-07-21T16:54:24+00:00urn:sha1:5e3eb2512591df0cef52404f0ea4202f58935a54
gpu offload host code generation
r? ghost
This will generate most of the host side code to use llvm's offload feature.
The first PR will only handle automatic mem-transfers to and from the device.
So if a user calls a kernel, we will copy inputs back and forth, but we won't do the actual kernel launch.
Before merging, we will use LLVM's Info infrastructure to verify that the memcopies match what openmp offloa generates in C++. `LIBOMPTARGET_INFO=-1 ./my_rust_binary` should print that a memcpy to and later from the device is happening.
A follow-up PR will generate the actual device-side kernel which will then do computations on the GPU.
A third PR will implement manual host2device and device2host functionality, but the goal is to minimize cases where a user has to overwrite our default handling due to performance issues.
I'm trying to get a full MVP out first, so this just recognizes GPU functions based on magic names. The final frontend will obviously move this over to use proper macros, like I'm already doing it for the autodiff work.
This work will also be compatible with std::autodiff, so one can differentiate GPU kernels.
Tracking:
- https://github.com/rust-lang/rust/issues/131513
add various wrappers for gpu code generation2025-07-18T23:24:12+00:00Manuel Drehwaldgit@manuel.drehwald.info2025-07-02T23:35:57+00:00urn:sha1:5958ebe829429e3595e8211e6cb1b0328d515ab7Pass wasm exception model to TargetOptions2025-07-18T07:35:50+00:00Nikita Popovnpopov@redhat.com2025-07-11T08:11:03+00:00urn:sha1:12b19be741ea07934d7478bd8e450dca8f85afe5
This is no longer implied by -wasm-enable-eh.
Shrink some `unsafe` blocks in cg_llvm2025-07-14T08:27:08+00:00Oli Scherergithub333195615777966@oli-obk.de2025-07-09T09:23:05+00:00urn:sha1:e574fef728605089da8144960348469896751c3cAvoid a bunch of unnecessary `unsafe` blocks in cg_llvm2025-07-14T08:27:08+00:00Oli Scherergithub333195615777966@oli-obk.de2025-07-09T09:12:42+00:00urn:sha1:d3d51b4fdbd6854da015f501e6566ca17cb023e5Auto merge of #142911 - mejrs:unsized, r=compiler-errors2025-07-11T05:27:32+00:00borsbors@rust-lang.org2025-07-11T05:27:32+00:00urn:sha1:855e0fe46e68d94e9f6147531b75ac2d488c548e
Remove support for dynamic allocas
Followup to rust-lang/rust#141811
Rollup merge of #143722 - oli-obk:sound-llvm, r=dianqk2025-07-11T00:20:39+00:00Trevor Grosst.gross35@gmail.com2025-07-11T00:20:39+00:00urn:sha1:6e3d017b2ff771438011feb5c21e0892ec2a22fb
Make some "safe" llvm ops actually sound
Noticed while doing other refactorings
it may cause some extra unnecessary allocations, but the current use sites are rare ones anyway
Make some "safe" llvm ops actually sound2025-07-10T07:27:41+00:00Oli Scherergithub333195615777966@oli-obk.de2025-07-10T07:27:41+00:00urn:sha1:84eeca2e2fc40bb8d6641846f18af9d8fc6a9681fix: correct parameter names in LLVMRustBuildMinNum and LLVMRustBuildMaxNum FFI declarations2025-07-08T11:24:19+00:00Dillon Amburgeydillona@dillona.com2025-07-08T11:17:03+00:00urn:sha1:045557797431bfff807145341efbe8f8fb08817eRemove support for dynamic allocas2025-07-07T21:04:06+00:00mejrs59372212+mejrs@users.noreply.github.com2025-06-24T14:58:46+00:00urn:sha1:49421d1fa382fba84792e5d5dd7721c1c3e0e46e