On 2015/10/16 14:28, David Coppa wrote: > So, the only downside seems to be performance related. > > See: https://bugzilla.mozilla.org/show_bug.cgi?id=1215479 > > <<iOS requires it (because it doesn't allow allocating RWX memory), but it's > not > enabled elsewhere because it's a performance hit (we should remeasure how much > though). This is because we have to toggle pages from executable to writable > and back whenever we patch JIT code>> > > What about enabling it in our port and see how it will end up? > We can always re-disable it at any time if people complain...
If it's not too much of a performance hit for iOS devices (i.e. small machines with arm cpu), it should be fine on a standard workstation-type machine like people would normally use to run Firefox on OpenBSD. And people have a relatively easy fallback of firefox-esr if they run into runtime problems. +1 from me for enabling in our port.
