-
Notifications
You must be signed in to change notification settings - Fork 12.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
target mipsel-unknown-linux-gnu standard libraries problem #102638
Comments
We've had that cpu level since #48874, configured here: rust/compiler/rustc_target/src/spec/mipsel_unknown_linux_gnu.rs Lines 11 to 12 in 0922559
And big-endian has been mips32r2 since #31303. |
The nightly compiler stated to build without error yesterday (cargo configurations uploaded under 'date'.txt).
As I am now able to generate what I want, and can generate other libraries as desired, I will be happy if you close this problem. |
Ok, if you're satisfied, I will close this. |
Problem
I have sucessfully compiled a static librsvg for 10 targets (1 native and 9 crosses) but my last target is giving me problems.
"export RUSTFLAGS='-C target-cpu=mips32'" sorts out the code in the tarball but I still have unimplemented opcodes in the compiler libraries for target mipsel-unknown-linux-gnu (see "unimplemented opcodes.txt") i.e. opcodes for mips32r2 (i.e. mips32 version 2 as per gcc compiler default, not version 1 as per my target).
I then installed Xargo to try and produce a set of standard libraries that can be run by every processor in the supported cpu list for the target. It fails on the last step with an internal compiler error (see "rust error.txt", the ... represents every step with no error, as re-iterated in the error message).
As Xargo is based on the nightly build, if I just have to wait for the internal bug to be fixed so I can generate my own standard libraries that is fine.
rust error.txt
unimplemented opcodes.txt
Please note that my prefered solution is that the standard libraries for rust can be executed by every cpu on the supported list for the target.
Steps
No response
Possible Solution(s)
No response
Notes
No response
Version
The text was updated successfully, but these errors were encountered: