rust/compiler/rustc_llvm/llvm-wrapper/LLVMWrapper.h, branch stablehttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=stable2024-11-09T09:46:08+00:00Auto merge of #132584 - Zalathar:includes, r=cuviper2024-11-09T09:46:08+00:00borsbors@rust-lang.org2024-11-09T09:46:08+00:00urn:sha1:4b198d6871e4a3826f01f7d6111b1c3484853cd8
Trim and tidy includes in `rustc_llvm`
These includes tend to accumulate over time, and are usually only removed when something breaks in a new LLVM version, so it's nice to clean them up manually once in a while.
General strategy used for this PR:
- Remove all includes from `LLVMWrapper.h` that aren't needed by the header itself, transplanting them to individual source files as necessary.
- For each source file, temporarily remove each include if doing so doesn't cause a compile error.
- If a “required” include looks like it shouldn't be needed, try replacing it with its sub-includes, then trim that list.
- After doing all of the above, go back and re-add any removed include if the file does actually use things defined in that header, even if the header happens to also be included by something else.
Make `RustString` an extern type to avoid `improper_ctypes` warnings2024-11-09T00:07:44+00:00ZalatharZalathar@users.noreply.github.com2024-11-03T01:40:26+00:00urn:sha1:89d7efaf8f5ed8c1c15faea21824ae479656bdc1Trim and tidy includes in `rustc_llvm`2024-11-04T05:35:39+00:00ZalatharZalathar@users.noreply.github.com2024-11-03T10:09:01+00:00urn:sha1:920d2774ac92b102dedf07d04d5fd80214881699Move `LLVMRustAttribute[Kind]` out of `LLVMWrapper.h`2024-11-04T01:27:23+00:00ZalatharZalathar@users.noreply.github.com2024-11-04T01:11:01+00:00urn:sha1:44a056a50b5eecad9e16188d18ea55011c153e7arustc_llvm: update for llvm/llvm-project@2ae968a0d9fb61606b020e898d884c82dd0ed8b52024-09-16T23:53:13+00:00Augie Fackleraugie@google.com2024-09-16T19:18:08+00:00urn:sha1:1e68f05109201c5920607e968fc9a1c4e4221b31
Just a simple header move.
@rustbot label: +llvm-main
Set writable and dead_on_unwind attributes for sret arguments2024-04-25T02:43:47+00:00Nikita Popovnpopov@redhat.com2024-02-19T14:02:49+00:00urn:sha1:3695af697efa26b0ea3b67739ade3ecc3929154eRemove `ffi_returns_twice` feature2024-01-30T22:09:09+00:00clubby789jamie@hill-daniel.co.uk2024-01-30T20:55:56+00:00urn:sha1:73313158988c20b57a341502b4099629b6867755Rollup merge of #118177 - sivadeilra:suppress-llvm-warnings, r=cuviper2023-12-06T20:52:31+00:00Matthias Krügermatthias.krueger@famsik.de2023-12-06T20:52:31+00:00urn:sha1:78d2061390f10a41a03618677c53dbee33af0d67
Suppress warnings in LLVM wrapper when targeting MSVC
The LLVM header files generate many warnings when compiled using MSVC. This makes it difficult to work on the LLVM wrapper code, because the warnings and errors that are relevant to local edits are obscured by the hundreds of lines of warnings from the LLVM Headers.
Add `-Zfunction-return={keep,thunk-extern}` option2023-11-30T19:21:31+00:00Miguel Ojedaojeda@kernel.org2023-10-18T14:58:17+00:00urn:sha1:2d476222e8458aa873e6760aac189b5e9d0a9930
This is intended to be used for Linux kernel RETHUNK builds.
With this commit (optionally backported to Rust 1.73.0), plus a
patched Linux kernel to pass the flag, I get a RETHUNK build with
Rust enabled that is `objtool`-warning-free and is able to boot in
QEMU and load a sample Rust kernel module.
Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
suppress warnings on msvc2023-11-22T17:10:53+00:00Arlie Davisardavis@microsoft.com2023-11-22T17:10:53+00:00urn:sha1:6773fd1a9a9aae8da53596e15eb2098e0efbb9a2