rust/compiler/rustc_llvm/llvm-wrapper/PassWrapper.cpp, branch 1.79.0https://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=1.79.02024-03-17T17:11:04+00:00Update the minimum external LLVM to 172024-03-17T17:11:04+00:00Josh Stonejistone@redhat.com2024-03-16T01:43:19+00:00urn:sha1:29430554f65619007f004e7941b7c2efb6465dbfPassWrapper: update for llvm/llvm-project@a3319371970b2024-03-07T15:24:48+00:00Augie Fackleraugie@google.com2024-03-07T14:49:15+00:00urn:sha1:ef626d772f7ee9ddba526b0693993f6479ee5c14
@rustbot label: +llvm-main
Explicitly assign constructed C++ classes2024-03-06T05:15:56+00:00Jubilee Youngworkingjubilee@gmail.com2024-03-06T04:04:24+00:00urn:sha1:23623a08d6a181864a7b8609682eee27534b12f4
C++ style guides I am aware of recommend specifically preferring = syntax
for any classes with fairly obvious constructors[^0] that do not perform
any complicated logic in their constructor. I contend that all constructors
that the `rustc_llvm` code uses qualify. This has only become more common
since C++ 17 guaranteed many cases of copy initialization elision.
The other detail is that I tried to ask another contributor with
infinitely more C++ experience than me (i.e. any) what this constructor
syntax was, and they thought it was a macro. I know of no other language
that has adopted this same syntax. As the rustc codebase features many
contributors experienced in many other languages, using a less...
unique... style has many other benefits in making this code more
lucid and maintainable, which is something it direly needs.
[^0]: e.g. https://abseil.io/tips/88
Add initial support for DataFlowSanitizer2024-03-02T02:50:40+00:00Ramon de C Vallercvalle@users.noreply.github.com2024-02-01T21:16:30+00:00urn:sha1:dee4e02102197adc29be9bf98083297dd3f5e2ed
Adds initial support for DataFlowSanitizer to the Rust compiler. It
currently supports `-Zsanitizer-dataflow-abilist`. Additional options
for it can be passed to LLVM command line argument processor via LLVM
arguments using `llvm-args` codegen option (e.g.,
`-Cllvm-args=-dfsan-combine-pointer-labels-on-load=false`).
Auto merge of #120055 - nikic:llvm-18, r=cuviper2024-02-13T15:07:28+00:00borsbors@rust-lang.org2024-02-13T15:07:28+00:00urn:sha1:eaff1af8fdd18ee3eb05167b2836042b7d4315f6
Update to LLVM 18
LLVM 18 final is planned to be released on Mar 5th. Rust 1.78 is planned to be released on May 2nd.
Tested images: dist-x86_64-linux, dist-s390x-linux, dist-aarch64-linux, dist-riscv64-linux, dist-loongarch64-linux, dist-x86_64-freebsd, dist-x86_64-illumos, dist-x86_64-musl, x86_64-linux-integration, test-various, armhf-gnu, i686-msvc, x86_64-msvc, i686-mingw, x86_64-mingw, x86_64-apple-1, x86_64-apple-2, dist-aarch64-apple
r? `@ghost`
Use MCSubtargetInfo::getAllProcessorFeatures()2024-02-13T09:33:40+00:00Nikita Popovnpopov@redhat.com2024-01-17T14:05:18+00:00urn:sha1:a911c8ce23a29a0721fb02ff90368143e764de9c
This method is now available in upstream LLVM \o/
PassWrapper: adapt for llvm/llvm-project@93cdd1b5cfa3735c599949b77e24dbfbe570441a2024-02-13T00:13:09+00:00Augie Fackleraugie@google.com2024-02-13T00:13:09+00:00urn:sha1:9d1bd2e067a82d6a2552b3705bbe6f256e9bde0c
Should be no functional change.
@rustbot label: +llvm-main
review2024-02-06T09:44:40+00:00klensyklensy@users.noreply.github.com2024-02-06T09:44:40+00:00urn:sha1:ca35cfb6defe6bdec8ab0419aa682db780142fb7llvm-wrapper: remove llvm 12 hack2024-02-06T09:24:30+00:00klensyklensy@users.noreply.github.com2024-01-26T08:36:56+00:00urn:sha1:2a06b69ba2600dbcd599641923fdc23b66344f9c
effectively reverts https://github.com/rust-lang/rust/commit/9a8acea78355b604dbeb29bc38bd4dbf7bfce95f
Revert "Auto merge of #113923 - DianQK:restore-no-builtins-lto, r=pnkfelix"2024-01-12T10:23:04+00:00DianQKdianqk@dianqk.net2024-01-12T10:23:04+00:00urn:sha1:aa874c5513803c074cf06df1adbde27f36f39439
This reverts commit 8c2b57721728233e074db69d93517614de338055, reversing
changes made to 9cf18e98f82d85fa41141391d54485b8747da46f.