Update compiler-builtins and enable f128 tests on all non-buggy platforms

[tgross35]

Update compiler_builtins to 0.1.138 and pin it. This updates to a new version of builtins that includes 1, which was
the last blocker to us enabling f128 tests on all platforms.

With that, we now provide symbols necessary to work with f128 everywhere. This means that we are no longer restricted to systems that provide f128 symbols themselves, and can enable tests by default.

There are still a handful of platforms that need to remain disabled because of bugs and some that had to get updated.

Math support is still off by default since those symbols are not yet available.

try-job: test-various
try-job: i686-gnu-nopt

[rustbot]

r? @workingjubilee

rustbot has assigned @workingjubilee.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

[rustbot]

These commits modify the library/Cargo.lock file. Unintentional changes to library/Cargo.lock can be introduced when switching branches and rebasing PRs.

If this was unintentional then you should revert the changes before this PR is merged.
Otherwise, you can ignore this comment.

The list of allowed third-party dependencies may have been modified! You must ensure that any new dependencies have compatible licenses before merging.

cc @davidtwco, @wesleywiser

[tgross35]

This includes #132433 which includes #132206, so the chain is a bit deep (I'm keeping updates separate from rust-lang/rust changes so we aren't blocked from updating further if something goes wrong here). But that doesn't mean we can't start some tests.

@bors try

[tgross35]

Those are quite a few try jobs but it still doesn't cover everything that will be newly enabled here.

@bors rollup=never

[bors]

⌛ Trying commit 15075bf with merge ec0220a...

[tgross35]

Also cc @beetrees

[bors]

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

[workingjubilee]

This has a merge conflict, it seems.

[workingjubilee]

I have rebased it.

[beetrees]

I think the f128 tests need to be disabled on 32-bit x86 due to llvm/llvm-project#77401 (although tests might pass anyway if the symbols from the LLVM-compiled compiler-builtins get picked by the linker instead of those from a GCC-compiled system library).

Also mips64/mips64r6 currently doesn't have f128 builtins built for it due to llvm/llvm-project#96432.

[workingjubilee]

I do not believe we run the relevant tests on mips64?

[workingjubilee]

I decided to change up the suite of tests slightly and rerun this. In particular, I noticed we didn't run the infamous test-various.

@bors try

[bors]

⌛ Trying commit 95998ee with merge ad17ccb...

[beetrees]

I do not believe we run the relevant tests on mips64?

All MIPS targets are tier 3, so no builds or tests of any kind are run by rust-lang/rust. The benefit of adding it to the match statement is just for those running tests locally/Linux distros with a MIPS64 port etc. 32-bit sparc is also tier 3 only and is already on the list.