rust/compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp, branch 1.81.0https://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=1.81.02024-07-12T20:15:10+00:00Remove LLVMRustDIBuilderInsertDeclareAtEnd return value2024-07-12T20:15:10+00:00Nikita Popovnpopov@redhat.com2024-07-12T12:52:26+00:00urn:sha1:8dfd3a455dc7d309f0c82dcb2e2f41da14f6c4af
The return value changed from an Instruction to a DbgRecord in
LLVM 19. As we don't actually use the result, drop the return
value entirely to support both.
Format C++ files in `llvm-wrapper`2024-06-26T12:18:49+00:00DianQKdianqk@dianqk.net2024-06-04T14:46:20+00:00urn:sha1:e17c16d55b20b9d2702fafa017263406d1e94042Auto merge of #121298 - nikic:writable, r=cuviper2024-04-25T04:31:56+00:00borsbors@rust-lang.org2024-04-25T04:31:56+00:00urn:sha1:284f94f9c0f77ad4ef85323a634cfda29c1a801d
Set writable and dead_on_unwind attributes for sret arguments
Set the `writable` and `dead_on_unwind` attributes for `sret` arguments. This allows call slot optimization to remove more memcpy's.
See https://llvm.org/docs/LangRef.html#parameter-attributes for the specification of these attributes. In short, the statement we're making here is that:
* The return slot is writable.
* The return slot will not be read if the function unwinds.
Fixes https://github.com/rust-lang/rust/issues/90595.
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:3695af697efa26b0ea3b67739ade3ecc3929154eRollup merge of #124132 - RalfJung:OpBundlesIndirect, r=Mark-Simulacrum2024-04-20T20:45:37+00:00许杰友 Jieyou Xu (Joe)39484203+jieyouxu@users.noreply.github.com2024-04-20T20:45:37+00:00urn:sha1:726361caf463d1419e99b34d82df5d1656a583e4
llvm RustWrapper: explain OpBundlesIndirect argument type
Follow-up to https://github.com/rust-lang/rust/pull/123941
r? ``@Mark-Simulacrum``
coverage. Lowering MC/DC statements to llvm-ir2024-04-19T16:34:40+00:00zhuyunxingzhuyunxing.zyx@alibaba-inc.com2024-04-19T02:58:16+00:00urn:sha1:439dbfa1ecb1b45db0acc728094d6e8ed3dc3080llvm RustWrapper: explain OpBundlesIndirect argument type2024-04-18T19:43:52+00:00Ralf Jungpost@ralfj.de2024-04-18T19:43:52+00:00urn:sha1:61def018c141964671c2a08180e234d46f188b0dFix UB in LLVM FFI when passing zero or >1 bundle2024-04-15T02:18:33+00:00Mark Rousskovmark.simulacrum@gmail.com2024-04-14T19:48:05+00:00urn:sha1:bf3deccdadffbd5903268cca74a60f7101f7e9c3
Rust passes a *const &OperandBundleDef to these APIs, usually from a
Vec<&OperandBundleDef> or so. Previously we were dereferencing that
pointer and passing it to the ArrayRef constructor with some length (N).
This meant that if the length was 0, we were dereferencing a pointer to
nowhere, and if the length was >1 then loading the *second* element
somewhere in LLVM would've been reading past the end.
Since Rust can't hold OperandBundleDef by-value we're forced to indirect
through a vector that copies out the OperandBundleDefs from the
by-reference list on the Rust side in order to match the LLVM expected
API.
Rollup merge of #123612 - kxxt:riscv-target-abi, r=jieyouxu,nikic,DianQK2024-04-10T02:27:40+00:00Matthias Krügermatthias.krueger@famsik.de2024-04-10T02:27:40+00:00urn:sha1:2ddf984594519c62ee23f0289a1a0afebb90186b
Set target-abi module flag for RISC-V targets
Fixes cross-language LTO on RISC-V targets (Fixes #121924)
Pass value and valueLen to create a StringRef2024-04-09T06:53:11+00:00Levi Zimrsworktech@outlook.com2024-04-09T06:47:06+00:00urn:sha1:33db20978e8157f53ca24fce1c54a7b5e07159cf
Instead of creating a cstring.
Co-authored-by: LoveSy <shana@zju.edu.cn>