Disable ThinLTO for x86_64-unknown-linux-gnu

[Mark-Simulacrum]

r? @Mark-Simulacrum

I am opening this to get performance numbers back. I believe it should fix #76980 and is largely something I'd be comfortable putting into stable while we work out the more difficult options on nightly (and perhaps beta).

[Mark-Simulacrum]

@rust-timer queue @bors try

[rust-timer]

Awaiting bors try build completion

[bors]

⌛ Trying commit f135c38 with merge 6f967be1d4ff00423ed16df7cb77f4074a9d6b80...

[bors]

☀️ Try build successful - checks-actions, checks-azure
Build commit: 6f967be1d4ff00423ed16df7cb77f4074a9d6b80 (6f967be1d4ff00423ed16df7cb77f4074a9d6b80)

[rust-timer]

Queued 6f967be1d4ff00423ed16df7cb77f4074a9d6b80 with parent 9fdaeb3, future comparison URL.

[rust-timer]

Finished benchmarking try commit (6f967be1d4ff00423ed16df7cb77f4074a9d6b80): comparison url.

Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. Please note that if the perf results are neutral, you should likely undo the rollup=never given below by specifying rollup- to bors.

Importantly, though, if the results of this run are non-neutral do not roll this PR up -- it will mask other regressions or improvements in the roll up.

@bors rollup=never