On Sun, Nov 24, 2024 at 01:25:59PM +0100, Iustin Pop wrote: > > >> B) bump the i386 baseline in Debian to require SSE2, and stop disabling > > >> SSE2 there in rustc > > >> C) disable all optimizations for Rust code on i386 (not really an option > > >> I think, just here for completeness sake) > > > > > > D) follow the other teams and stop building Rust on i386. > > > > I am not personally invested in i386 at all, but that is still not a call > > that I'd want to make as toolchain maintainer. If the release team prefers > > it over B) and over risking running into the miscompilation issues in > > practice, then I won't object. > > > > FWIW, my (personal!) current preference would be B), followed by either > > documenting the issue and accepting it or D). Given the far-reaching > > implications of both B and D, I don't think this is a decision that either > > I or the Rust team can make alone. > > I've been watching this thread from the sideline so far, but after > thinking some more, I don't understand why B) is simply not the chosen > path forward.
Nobody has made the choice or asked relevant people to make a choice, and relevant people haven't commented on this, to my knowledge (RT by their own 2023 update are *not* relevant people wrt raising the baseline). And among people who cannot make this choice but voice their opinion (or explicitly decline to have one) many are either conservative or think that the project is, or should be, conservative. In other words, I feel like in this specific case having many people on mailing lists hesitating about this doesn't mean the project won't do that in the near future. -- WBR, wRAR
signature.asc
Description: PGP signature
