So I reran the analysis, this time breaking down by OS the users who we can't say for certain have SSE2: https://gist.github.com/chutten/e4ccd0d5a46b782bae53
This was on a 25% sample of users reporting in from release Firefox on Jan 21. The tl;dr is that it's mostly WinXP. So much so that it's almost correct to say that it's _only_ WinXP. :chutten On Wed, Feb 3, 2016 at 9:41 AM, Ehsan Akhgari <ehsan.akhg...@gmail.com> wrote: > On 2016-02-03 8:23 AM, Henri Sivonen wrote: > >> For Rust code that doesn't explicitly try to use SSE2, are we going to >> use the default official rustc which emits SSE2-requiring code and, >> therefore, make Firefox require SSE2 on 32-bit x86? Or are we going to >> use rustc in a non-default configuration so that SSE2 instructions are >> absent in its output and, therefore, we'd ship using a non-default >> compiler config? (I'm hoping this gets decided before figuring it out >> becomes a blocker. If it has been already figured out, awesome.) >> > > The rust driver added support for target-feature here: < > https://github.com/rust-lang/rust/pull/5996> This allows control over > the target features the LLVM codegen assumes. It seems like passing -C > target-feature=-sse2 will make rust not emit SSE2 instructions (but I > haven't tested this.) > > Do you mind giving this a shot? > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
