diff options
| author | bors <bors@rust-lang.org> | 2017-04-07 08:36:11 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2017-04-07 08:36:11 +0000 |
| commit | 4c59c92bc4d4d6e5b2b66c4cc08dd1a058283a0d (patch) | |
| tree | 3ac2a85c507f549dfc2c8720419cad0fa64eacee /src/rustllvm/PassWrapper.cpp | |
| parent | b9c5197d4878253804d91e0c30ed92e0a965b663 (diff) | |
| parent | aab2cca046670295bc1a430a8b1c23d755f9bd5a (diff) | |
| download | rust-4c59c92bc4d4d6e5b2b66c4cc08dd1a058283a0d.tar.gz rust-4c59c92bc4d4d6e5b2b66c4cc08dd1a058283a0d.zip | |
Auto merge of #40873 - cramertj:on-demandify-queries, r=nikomatsakis
On demandify reachability cc https://github.com/rust-lang/rust/issues/40746 I tried following this guidance from #40746: > The following tasks currently execute before a tcx is built, but they could be easily converted into queries that are requested after tcx is built. The main reason they are the way they are was to avoid a gratuitious refcell (but using the refcell map seems fine)... but the result of moving `region_maps` out of `TyCtxt` and into a query caused a lot of churn, and seems like it could potentially result in a rather large performance hit, since it means a dep-graph lookup on every use of `region_maps` (rather than just a field access). Possibly `TyCtxt` could store a `RefCell<Option<RegionMap>>` internally and use that to prevent repeat lookups, but that feels like it's duplicating the work of the dep-graph. @nikomatsakis What did you have in mind for this?
Diffstat (limited to 'src/rustllvm/PassWrapper.cpp')
0 files changed, 0 insertions, 0 deletions