Update cc for remaining lockfiles

[ognevny]

I forgot to update cc in compile-benchmarks crates. when I tried to do so, I found that not all packages got rquired version of cc (>=1.1.10), so I just blibfly ran cargo update for all packages to guarantee fresh version of cc...

[ognevny]

this is a very huge diff. I'll try to update crates for each package manually

[ognevny]

@Kobzol sorry for disturbing with my attempts on making opt-dist work for specific host. I tried to minimize diff here, but I didn't manage to win cargo in fight with cc update for cargo-0.60.0 (it updates cc to >=v1.1.10 only with full lockfile update)

edit: done, minimized the diff :)

[Kobzol]

Hmm, I have much bigger issue with this than the previous PR :) We only update the compile benchmarks if they stop compiling on our supported targets (which is right pretty much only x64 Linux), to keep benchmark stability.

I don't want to do these global lockfile updates for the benchmarks in a single PR.

That being said, we are currently just before a big benchmark update that will update most of the benchmarks to newer versions, which should also bump cc. So after that update the situation might be better for your target. The update will take at least several weeks though (and someone actually has to start doing it..).

#2024

[ognevny]

understood. I'll use my patch downstream then. waiting for updates

[ognevny]

by the way, when you open a PR with compile-benchmark, please mork your PR with closes #2067 so I'll get a notification when your PR is merged :)

[Kobzol]

There will probably be ~50 of such PRs (we need on PR to add a new benchmark and then later to remove the old one). I created a benchmark-update label to track this.