Add missing target-abi to cross-lang llvm lto bitcode

[yujincheng08]

When linker_plugin_lto enabled, we need to add target-abi to the generated llvm bitcode, otherwise there may be an error like "cannot link object files with different floating-point ABI".

[rustbot]

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @compiler-errors (or someone else) some time within the next two weeks.

Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (S-waiting-on-review and S-waiting-on-author) stays updated, invoking these commands when appropriate:

• @rustbot author: the review is finished, PR author should check the comments and take action accordingly
• @rustbot review: the author is ready for a review, this PR will be queued again in the reviewer's queue

[compiler-errors]

r? @wesleywiser or @cuviper perhaps?

[yujincheng08]

r? @cuviper

[cuviper]

Is there a test we can add for this?

For most targets, this will be an empty string, and we already set it when creating the target machine. I'm surprised that this would need to be repeated in module options, and I can only find one place where clang does this, only on RISC-V:
https://github.com/llvm/llvm-project/blob/d345f6a25343f926f55e70b442dfa507ba31b597/clang/lib/CodeGen/CodeGenModule.cpp#L1089-L1093

@rust-lang/wg-llvm, anyone else have a better idea of expectations here?

[DianQK]

I'd like to first see a specific error log if adding a test case is challenging.

[nikic]

It looks like another PR for the same issue with a test has been opened here: #123612

[yujincheng08]

Thanks. close in flavor of #123612