Get rid of native_library projection queries

[Noratrieb]

They don't seem particularly useful as I don't expect native libraries to change frequently.

Maybe they do provide significant value of keeping incremental compilation green though, I'm not sure.

[rust-highfive]

r? @jackh726

(rust-highfive has picked a reviewer for you, use r? to override)

[Noratrieb]

r? @cjgillot

[cjgillot]

@bors try @rust-timer queue

[rust-timer]

Awaiting bors try build completion.

@rustbot label: +S-waiting-on-perf

[bors]

⌛ Trying commit c41bc6d2c7fac5d098e3fe07ef97a205cb9617ea with merge eaaecf18de006f1c6980d0259087f73851f83001...

[bors]

☀️ Try build successful - checks-actions
Build commit: eaaecf18de006f1c6980d0259087f73851f83001 (eaaecf18de006f1c6980d0259087f73851f83001)

[rust-timer]

Queued eaaecf18de006f1c6980d0259087f73851f83001 with parent 21b2465, future comparison URL.

[rust-timer]

Finished benchmarking commit (eaaecf18de006f1c6980d0259087f73851f83001): comparison URL.

Overall result: ✅ improvements - no action needed

Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR may lead to changes in compiler perf.

@bors rollup=never
@rustbot label: +S-waiting-on-review -S-waiting-on-perf -perf-regression

Instruction count

This is a highly reliable metric that was used to determine the overall result at the top of this comment.

	mean1	range	count2
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-0.4%	[-0.5%, -0.2%]	6
All ❌✅ (primary)	-	-	0

Max RSS (memory usage)

This benchmark run did not return any relevant results for this metric.

Cycles

Results

This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.

	mean1	range	count2
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	2.2%	[2.2%, 2.2%]	1
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	-	-	0

Footnotes

1. the arithmetic mean of the percent change ↩ ↩²

2. number of relevant changes ↩ ↩²

[Noratrieb]

The externs benchmark got faster, nice, that sounds relevant :)

[cjgillot]

Thanks @Nilstrieb.
@bors r+

[bors]

📌 Commit c41bc6d2c7fac5d098e3fe07ef97a205cb9617ea has been approved by cjgillot

It is now in the queue for this repository.

[bors]

🔒 Merge conflict

This pull request and the master branch diverged in a way that cannot be automatically merged. Please rebase on top of the latest master branch, and let the reviewer approve again.

How do I rebase?

Assuming self is your fork and upstream is this repository, you can resolve the conflict following these steps:

1. git checkout no-meta-query (switch to your branch)
2. git fetch upstream master (retrieve the latest master)
3. git rebase upstream/master -p (rebase on top of it)
4. Follow the on-screen instruction to resolve conflicts (check git status if you got lost).
5. git push self no-meta-query --force-with-lease (update this PR)

You may also read Git Rebasing to Resolve Conflicts by Drew Blessing for a short tutorial.

Please avoid the "Resolve conflicts" button on GitHub. It uses git merge instead of git rebase which makes the PR commit history more difficult to read.

Sometimes step 4 will complete without asking for resolution. This is usually due to difference between how Cargo.lock conflict is handled during merge and rebase. This is normal, and you should still perform step 5 to update this PR.

Error message

Auto-merging compiler/rustc_middle/src/query/mod.rs
CONFLICT (content): Merge conflict in compiler/rustc_middle/src/query/mod.rs
Automatic merge failed; fix conflicts and then commit the result.

[Noratrieb]

I rebased the merge conflict, can I get an r+ again?

[jyn514]

@bors r=cjgillot

[bors]

📌 Commit ccc5461 has been approved by cjgillot

It is now in the queue for this repository.

[bors]

⌛ Testing commit ccc5461 with merge 3022afe...

[bors]

☀️ Test successful - checks-actions
Approved by: cjgillot
Pushing 3022afe to master...

[rust-timer]

Finished benchmarking commit (3022afe): comparison URL.

Overall result: ✅ improvements - no action needed

@rustbot label: -perf-regression

Instruction count

This is a highly reliable metric that was used to determine the overall result at the top of this comment.

	mean1	range	count2
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-0.5%	[-1.2%, -0.2%]	7
All ❌✅ (primary)	-	-	0

Max RSS (memory usage)

This benchmark run did not return any relevant results for this metric.

Cycles

This benchmark run did not return any relevant results for this metric.

Footnotes

1. the arithmetic mean of the percent change ↩

2. number of relevant changes ↩