Skip to content

Fix rlib creation. Change the filename of compressed bitcode - #13074

Merged
bors merged 1 commit into
rust-lang:masterfrom
pczarn:build-rlib
Mar 23, 2014
Merged

Fix rlib creation. Change the filename of compressed bitcode#13074
bors merged 1 commit into
rust-lang:masterfrom
pczarn:build-rlib

Conversation

@pczarn

Copy link
Copy Markdown
Contributor

Fixes#12992

I tried to increase the number of deflate's probes. Reduction of 0.5% or 2% is not enough.

@emberian

Copy link
Copy Markdown
Contributor

@pczarn next time can you put the "fixes ..." in the commit? makes it hard to understand a commit without looking at the PR

@pczarn

Copy link
Copy Markdown
ContributorAuthor

@cmr I'm going to fix this commit. I can't think of a portable way to test it.

@pczarn

Copy link
Copy Markdown
ContributorAuthor

Third attempt. I hope the bitcode can be reproduced with subsequent builds, and always will.

Fixesrust-lang#12992
Store compressed bitcode files in rlibs with a different extension. Compression doesn't interfere with --emit=bc.
Regression test compares outputs.
bors added a commit that referenced this pull request Mar 23, 2014
Fixes#12992
I tried to increase the number of deflate's probes. Reduction of 0.5% or 2% is not enough.
@borsbors closed this Mar 23, 2014
@bors
bors merged commit f0f5072 into rust-lang:masterMar 23, 2014
@pczarn
pczarn deleted the build-rlib branch January 14, 2015 16:58
lnicola pushed a commit to lnicola/rust that referenced this pull request Aug 23, 2022
…predicate, r=lowr
Consider bounds on inherent impl in method resolution
There are three type-related things we should consider in method resolution: `Self` type, receiver type, and impl bounds. While we check the first two and impl bounds on trait impls, we've been ignoring the impl bounds on inherent impls. With this patch rust-analyzer now takes them into account and is able to select the appropriate inherent method.
Resolvesrust-lang#5441Resolvesrust-lang#12308
bors added a commit to rust-lang-ci/rust that referenced this pull request Feb 25, 2024
Setup infra for handling auto trait bounds disabled due to perf problems
This patch updates some of the partially-implemented functions of `ChalkContext as RustIrDatabase`, namely `adt_datum()` and `impl_provided_for()`. With those, we can now correctly work with auto trait bounds and distinguish methods based on them.
Resolvesrust-lang#7856 (the second code; the first one is resolved by rust-lang#13074)
**IMPORTANT**: I don't think we want to merge this until rust-lang#7637 is resolved. Currently this patch introduces A LOT of unknown types and type mismtaches as shown below. This is because we cannot resolve items like `hashbrown::HashMap` in `std` modules, leading to auto trait bounds on them and their dependents unprovable.
|crate (from `rustc-perf@c52ee6` except for r-a)|e3dc5a588f07d6f1d3a0f33051d4af26190abe9e|HEAD of this branch|
|---|---|---|
|rust-analyzer @ e3dc5a5 |exprs: 417528, ??ty: 907 (0%), ?ty: 114 (0%), !ty: 1|exprs: 417528, ??ty: 1704 (0%), ?ty: 403 (0%), !ty: 20|
|ripgrep|exprs: 62120, ??ty: 2 (0%), ?ty: 0 (0%), !ty: 0|exprs: 62120, ??ty: 132 (0%), ?ty: 58 (0%), !ty: 11|
|webrender/webrender|exprs: 94355, ??ty: 49 (0%), ?ty: 16 (0%), !ty: 2|exprs: 94355, ??ty: 429 (0%), ?ty: 130 (0%), !ty: 7|
|diesel|exprs: 132591, ??ty: 401 (0%), ?ty: 5129 (3%), !ty: 31|exprs: 132591, ??ty: 401 (0%), ?ty: 5129 (3%), !ty: 31|
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Output of an --emit dependent on other outputs present

4 participants

@pczarn@emberian@alexcrichton@bors