rust/src/test/codegen/scalar-pair-bool.rs, branch 1.62.0https://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=1.62.02022-02-05T06:09:52+00:00Apply noundef attribute to &T, &mut T, Box<T>, bool2022-02-05T06:09:52+00:00Erik Desjardinserikdesjardins@users.noreply.github.com2022-02-05T06:00:37+00:00urn:sha1:8cb0b6ca5bf1321d38f4602113b0f41c837d0586
This doesn't handle `char` because it's a bit awkward to distinguish it
from u32 at this point in codegen.
Note that for some types (like `&Struct` and `&mut Struct`),
we already apply `dereferenceable`, which implies `noundef`,
so the IR does not change.
Manually set dso_local when its valid to do so2021-04-02T21:00:29+00:00Simonas Kazlauskasgit@kazlauskas.me2021-03-27T22:11:24+00:00urn:sha1:2f000a78bf615b35c4837f920fb6adcad4848351
This should have no real effect in most cases, as e.g. `hidden`
visibility already implies `dso_local` (or at least LLVM IR does not
preserve the `dso_local` setting if the item is already `hidden`), but
it should fix `-Crelocation-model=static` and improve codegen in
executables.
Note that this PR does not exhaustively port the logic in [clang]. Only
the obviously correct portion and what is necessary to fix a regression
from LLVM 12 that relates to `-Crelocation_model=static`.
Fixes #83335
[clang]: https://github.com/llvm/llvm-project/blob/3001d080c813da20b329303bf8f45451480e5905/clang/lib/CodeGen/CodeGenModule.cpp#L945-L1039
Match scalar-pair-bool more flexibly for LLVM 112020-08-22T20:44:54+00:00Josh Stonejistone@redhat.com2020-08-18T22:11:02+00:00urn:sha1:fb05be00df385ed216fcb9f6712206ec64fed72e
LLVM 11 started using `phi` and `select` for `fn pair_i32_bool`, which
is still valid, but harder to match than the simple instructions we were
getting before. We'll just check that the unpacked args are directly
referenced in any way, and call it good.
codegen: use "_N" (like for other locals) instead of "argN", for argument names.2019-09-13T16:25:05+00:00Eduard-Mihai Burtescuedy.burt@gmail.com2019-09-13T16:25:05+00:00urn:sha1:bdad2c52a538206a2f1c154bb5d5c3d7cb6b5d6fRemove licenses2018-12-26T04:08:33+00:00Mark Rousskovmark.simulacrum@gmail.com2018-12-25T15:56:47+00:00urn:sha1:2a663555ddf36f6b041445894a8c175cd1bc718cUpdate scalar pairs per review comments2018-07-05T21:22:09+00:00Josh Stonejistone@redhat.com2018-07-05T21:22:09+00:00urn:sha1:557736befc84fb72066128a8c42efe6e4e63a3b1Store scalar pair bools as i8 in memory2018-07-05T16:59:52+00:00Josh Stonejistone@redhat.com2018-06-15T22:47:54+00:00urn:sha1:e5789765606baebd983bd9b1c870cb8b57a0627b
We represent `bool` as `i1` in a `ScalarPair`, unlike other aggregates,
to optimize IR for checked operators and the like. With this patch, we
still do so when the pair is an immediate value, but we use the `i8`
memory type when the value is loaded or stored as an LLVM aggregate.
So `(bool, bool)` looks like an `{ i1, i1 }` immediate, but `{ i8, i8 }`
in memory. When a pair is a direct function argument, `PassMode::Pair`,
it is still passed using the immediate `i1` type, but as a return value
it will use the `i8` memory type. Also, `bool`-like` enum tags will now
use scalar pairs when possible, where they were previously excluded due
to optimization issues.