Re: Reverting to VS2013 on central and aurora

2016-05-16 Thread Henri Sivonen
On Fri, May 13, 2016 at 11:42 PM, Benjamin Smedberg wrote: > I am talking about requiring SSE2. That is a larger (but still quite small) > population, but the upside of being able to turn on SSE2 optimizations by > default is an important benefit. I've discussed and confirmed this with > Firefox p

[Firefox Desktop] Issues found: May 9th to May 13th

2016-05-16 Thread Andrei Vaida
Hi everyone, Here's the list of new issues found and filed by the Desktop Release QA Team last week, *May 09 - May 13* (week 19). Additional details on the team's priorities last week, as well as the plans for the current week are available at: https://public.etherpad-mozilla.org/p/Deskt

Re: Reverting to VS2013 on central and aurora

2016-05-16 Thread Benjamin Smedberg
On Mon, May 16, 2016 at 8:47 AM, Henri Sivonen wrote: > > > For clarification: Does this decision apply to 32-bit x86 Linux as > well? (It would be sad to have to supply and maintain non-SSE2 x86 > code paths just for Linux.) > Nobody asked about that, so it's wasn't specifically included. IIRC

Re: Reverting to VS2013 on central and aurora

2016-05-16 Thread Ralph Giles
On Mon, May 16, 2016 at 10:53 AM, Benjamin Smedberg wrote: > IIRC the Mozilla builds of Firefox for Linux already require SSE2 by virtue > of their -i686 build targeting, so the real question here is whether we > want to support distros that don't require SSE2? I'm ok with that, but I > don't whe

Re: Reverting to VS2013 on central and aurora

2016-05-16 Thread Mike Hommey
On Mon, May 16, 2016 at 01:53:51PM -0400, Benjamin Smedberg wrote: > On Mon, May 16, 2016 at 8:47 AM, Henri Sivonen > wrote: > > > > > > > For clarification: Does this decision apply to 32-bit x86 Linux as > > well? (It would be sad to have to supply and maintain non-SSE2 x86 > > code paths just

Re: Reverting to VS2013 on central and aurora

2016-05-16 Thread yuhongbao_386
On Saturday, May 7, 2016 at 2:18:05 AM UTC-7, Emanuel Hoogeveen wrote: > Well, I think that's debatable ;) The Athlon XP had clock speeds of up to > 2333MHz, though I'm sure the per-clock performance doesn't measure up to > current offerings. But Ion can easily be 5x as fast as Baseline. Of cours