Sergey Fedorov
Sergey Fedorov
> The compiler defaults to compiling for the architecture it's running on... but that error does seem to imply that there's a different architecture involved (and or something even stranger,...
@thepowersgang This was insightful: while it builds on PPC as a ppc binary, target settings are totally off: ``` /opt/local/var/macports/build/_opt_PPCSnowLeopardPorts_lang_mrustc/mrustc/work/thepowersgang-mrustc-1b1416b/bin/mrustc -Z print-cfgs sergey-fedorovs-power-mac-g5:~ svacchanda$ /opt/local/var/macports/build/_opt_PPCSnowLeopardPorts_lang_mrustc/mrustc/work/thepowersgang-mrustc-1b1416b/bin/mrustc -Z print-cfgs Setup: V V...
@thepowersgang _Possibly_ we need to set Bool to 4 bytes on `powerpc-apple-darwin` (only for ppc32, not ppc64). Could you advise how to do it? Possibly here: ``` TU_ARMA(Primitive, te) {...
@thepowersgang Target fixed: ``` svacchanda$ /opt/local/var/macports/build/_opt_PPCSnowLeopardPorts_lang_mrustc/mrustc/work/thepowersgang-mrustc-1b1416b/bin/mrustc -Z print-cfgs Setup: V V V (0.00 s) Setup: DONE Target Load: V V V (0.00 s) Target Load: DONE >rust_compiler=mrustc >target_arch=powerpc >target_endian=big >target_env=gnu...
With fixed target, x86 is no longer pulled, but `rust` fails almost immediately with this: ``` make[1]: Nothing to be done for `all'. test -e bin/mrustc /usr/bin/make -C tools/minicargo/ make[1]:...
Yeah, this code in `rust` is wrong: ``` /// Platform-specific intrinsics for the `PowerPC` platform. /// /// See the [module documentation](../index.html) for more details. #[cfg(any(target_arch = "powerpc", doc))] #[doc(cfg(target_arch =...
Altivec code appears broken, so I disabled it together with VSX in `rustc-1.54.0-src/library/stdarch/crates/core_arch/src/powerpc/mod.rs`. Build still fails though here: ``` test -e bin/minicargo bin/minicargo rustc-1.54.0-src/library/std --vendor-dir rustc-1.54.0-src/vendor --script-overrides script-overrides/stable-1.54.0-macos/ --output-dir output-1.54.0/...
> Re `bool`'s size: What what `rustc` does - that's the correct method. Then leave it as is.
> Re `Handle big endian in constant evaluate` - It looks to be relatively simple to implement, if you feel like it. @thepowersgang Could you please advise more specifically here,...
@thepowersgang Awesome, thank you! I should be able to test it in a few days (been away from my PPC hardware for a while, returning now). P. S. @catap FYI.