Use rust target triple instead of LLVM's

[antoyo]

No description provided.

[bjorn3]

This would break with custom targets. TargetTuple::tuple() returns the basename of the json file for custom targets, which has no relation to the underlying target that the codegen backend would generate code for.

[antoyo]

This would break with custom targets. TargetTuple::tuple() returns the basename of the json file for custom targets, which has no relation to the underlying target that the codegen backend would generate code for.

Using the LLVM target caused issues in the past.
Do you mean we should fix something on the bootstrap side as well?

[bjorn3]

I'm not sure there is a great fix. I guess keeping this code as is and accepting that libgccjit is found based on the json filename works for now.

[antoyo]

I'm not sure there is a great fix. I guess keeping this code as is and accepting that libgccjit is found based on the json filename works for now.

Isn't the current code broken for all arch where the LLVM target triple is different than Rust's target triple?

[bjorn3]

I meant keeping the code in this PR as is and merging this PR.

[antoyo]

Thanks.