about summary refs log tree commit diff
path: root/src/libcore/array
diff options
context:
space:
mode:
authorDylan DPC <dylan.dpc@gmail.com>2020-05-04 16:15:28 +0200
committerGitHub <noreply@github.com>2020-05-04 16:15:28 +0200
commitd47ec165826acd95893c5e76e506be3d22188c99 (patch)
tree47bd6d45e6cec9be5f2c83e78156e52d3744f583 /src/libcore/array
parent679431f7419e5fe2644a008092f00ccd36779dfb (diff)
parentd0dea9f5887c8371279b0b07ce0380f060ca1e99 (diff)
downloadrust-d47ec165826acd95893c5e76e506be3d22188c99.tar.gz
rust-d47ec165826acd95893c5e76e506be3d22188c99.zip
Rollup merge of #71697 - felix91gr:new_prop_into_fn_call, r=wesleywiser
Added MIR constant propagation of Scalars into function call arguments

Now for the function call arguments!

Caveats:
1. It's only being enabled at `mir-opt-2` or higher, because currently codegen gives performance regressions with this optimization.
2. Only propagates Scalars. Tuples and references (references are `Indirect`, right??) are not being propagated into as of this PR.
3. Maybe more tests would be nice?
4. I need (shamefully) to ask @wesleywiser to write in his words (or explain to me, and then I can write it down) why we want to ignore propagation into `ScalarPairs` and `Indirect` arguments.

r? @wesleywiser
Diffstat (limited to 'src/libcore/array')
0 files changed, 0 insertions, 0 deletions