On Sun, Feb 22, 2026 at 08:11:17PM +0100, Miguel Ojeda wrote: > On Sun, Feb 22, 2026 at 8:07 PM Link Mauve <[email protected]> wrote: > > > > Should we come back to describing the target like I did in my first > > patch[1] in scripts/generate_rust_target.rs, or should I bring that to > > Rust to create a powerpc-unknown-unknown-softfloat target upstream? Or > > is there a better third solution I’m not thinking of? > > We are trying to stop using the custom target specs, so we should ask > upstream to give you a built-in target you can use (or equivalently, a > flag to do what you need, but I think the idea is to not have such a > flag). > > i.e. even if you used the custom target JSON, we would still need to > ask, since the goal is to remove that script entirely. > > Thanks! > > Cheers, > Miguel
Sorry for the spam, my earlier message got rejected. I think, disabling altivec, fpu and vsx with compiler flag will work. What are your opinion on this? Regards, Mukesh
