On 2013-01-31 3:37 AM, Nicholas Nethercote wrote:
On Thu, Jan 31, 2013 at 3:03 PM, Ehsan Akhgari <ehsan.akhg...@gmail.com> wrote:
Given the above, I'd like to propose the following long-term solutions:
1. Disable PGO/LTCG now.
2. Try to delay disabling PGO/LTCG as much as possible.
3. Try to delay disabling PGO/LTCG until the next time that we hit the
limit, and disable PGO/LTCG then once and for all.
In the long run, 1 and 3 are the same. If we know we're going to turn
it off, why not bite the bullet and do it now? One big advantage of
that is that we'd immediately stop suffering through PGO-only bugs.
(I'm not necessarily advocating this, BTW, just observing that the two
options are basically equivalent.)
The PGO miscompilation bugs is a good point, thanks for bringing it up.
Also, stupid question time: is it possible to build on Windows with
GCC and/or clang?
I don't have a lot of experience with mingw32, but to the best of my
knowledge, it's based on older versions of gcc (4.6?), and lacks 64-bit
support plus a number of C++ runtime library features, and a number of
MSVC features, such as SEH.
Clang on Windows is further away, with incomplete support for the
Microsoft C++ ABI, inline assembly, and some compiler intrinsics. We
may be able to consider this when the situation improves.
Cheers,
Ehsan
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
