Re: Git mirror of mozilla-central down
> Unfortunately I don't have enough time for now to work on this even more, > so you should not expect any more updates to the mozilla-central mirror. I > may look at this again in the future and try other things that I can think > of (such as trying to narrow down the failure range even further, or > resorting to drastic measures such as redoing parts of the initial > conversion process from scratch), but I don't know when I will have enough > time to look at this again. If you're someone who knows things about git, > mercurial or hg-git and wants to lend a hand, I can provide you with more > information on how to reproduce the problem, and what I've tried and where > to go from here. I had the same problem with my Git mirror and I have it fixed for me. Ping me on IRC (nick jacek) and I'm happy to assist you with the problem. It shouldn't take much of your time. Cheers, Jacek ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: The future of PGO on Windows
> Also, stupid question time: is it possible to build on Windows with > GCC and/or clang? Yes, even better, it's possible to build on Linux for Windows using GCC, see: https://developer.mozilla.org/en-US/docs/Cross_Compile_Mozilla_for_Mingw32 It should be also possible to build on Windows, but AFAICS noone did it for a while, so it would probably require some fixes. Those builds are not yet feature complete, but it's just a matter of (usually not too hard) fixes. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: The future of PGO on Windows
W dniu czwartek, 31 stycznia 2013 14:21:06 UTC+1 użytkownik Joshua Cranmer napisał: > On 1/31/2013 2:37 AM, Nicholas Nethercote wrote: > > > Also, stupid question time: is it possible to build on Windows with > > > GCC and/or clang? > > > It's definitely possible to build with Mingw GCC, but that is a major > ABI-breaking change, Both extern "C" and XPCOM functions are ABI-compatible. The problem is only with "plain C++" calls, but those are mostly internal calls, so ABI breackage is not really a problem. > and I think we lose the ability to compile against > any Microsoft IDL interfaces. This is a common misunderstanding. Compiling against IDL-based interfaces has always been possible. The problem was with compiling (MS) IDL files itself (which is uncommon thing to do, only accessibility module does that in whole m-c tree) and even that's possible now. Jacek ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: The future of PGO on Windows
> 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 Currently the best option for mingw is mingw-w64 for that (besides what the name suggests) supports both 32 and 64-bit targets. Also it works with any version of GCC newer than 4.4, AFAIR. > plus a number of C++ runtime library features, mingw uses GCC's stdc++ and adds only a few limitations comparing to other stdc++ targets. > and a number of MSVC features, such as SEH. Yes, SEH is a problem. FWIW, GCC 4.8 will have limited SEH support for 64-bit targets. Jacek ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
