Re: Firefox and clang-cl

[cosinusoidally]

On Sunday, 13 August 2017 06:20:31 UTC+1, Mike Hommey  wrote:
> On Sat, Aug 12, 2017 at 11:22:30PM -0400, Jeff Muizelaar wrote:
> > On Sat, Aug 12, 2017 at 9:40 PM, Ehsan Akhgari  
> > wrote:
> > > Last but not least, you may ask yourself why would we want to spend this
> > > much effort to switch to clang-cl on Windows?  I believe this is an
> > > important long term shift that is beneficial for us.  First and foremost,
> > > clang is a vibrant open source compiler, and being able to use open source
> > > toolchains on our most important platforms is really important for us in
> > > terms of being able to contribute to the compiler where needed
> > 
> > It's worth emphasizing the value of using an open source compiler.
> > Being able to find and fix bugs in the compiler instead of having to
> > work around them without knowing the true cause is enormously
> > valuable. A recent example of this happened to me yesterday with
> > https://bugzilla.mozilla.org/show_bug.cgi?id=1382857. Once I had
> > reported the issue (https://bugs.llvm.org/show_bug.cgi?id=34163) a fix
> > was committed to clang trunk in less than 6 hours. That's something
> > not ever possible with MSVC.
> 
> That bugs can be fixed in a few hours is nice, but that's not the main
> advantage. (also, not all bugs are fixed in a few hours. The one that
> makes Firefox fail to build with current clang trunk has been open for 2
> weeks and hasn't been fixed yet).
> 
> The main advantage is that you can take that fix, and apply it to your
> compiler *right now*. As opposed to "whenever the vendor makes a new
> release". We're regularly applying patches to clang and GCC.  We can't
> do the same to MSVC, even when we file bugs to Microsoft and they fix
> them.
> 
> Another advantage is that if you're so inclined, you can fix the
> it yourself.
> 
> Mike
> 
> PS: And once clang-cl+lld actually works, it will also be possible to
> build for Windows on Linux.

Haven't you been able to do that with MinGW on Linux since about 1998?

Thanks
Liam Wilson
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: libc++ enabled for Android / C++11 standard library update

[cosinusoidally]

On Tuesday, 3 May 2016 16:32:55 UTC+1, Nicholas Alexander  wrote:
> On Tue, May 3, 2016 at 7:57 AM, Nathan Froyd  wrote:
> > This change leaves Mac as our only tier-1 platform without a C++11
> > standard library.

Out of interest, what is the situation on Linux? Which C++11 standard library 
will you be using? Will you be shipping your own copy as a shared library, or 
will you be using the system one?  If I understand correctly, I assume you 
cannot link against the libstdc++ that ships with GCC 4.8.5 as the libstdc++ 
C++11 ABI did not stabilise until GCC 5.X (meaning your binaries will not work 
properly unless the distro where you are running ships exactly the same 
libstdc++)?

Thanks
Liam Wilson
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: Linux distro readiness for Rust in Gecko

[cosinusoidally]

On Thursday, 17 March 2016 12:23:32 UTC, Henri Sivonen  wrote:
> On Thu, Mar 17, 2016 at 1:58 PM, Martin Stransky  wrote:
> > Is it possible to build Rust from sources before Firefox build executes?
> 
> rustc is written in Rust, so if you only have source code and the
> compilers that are currently available in Fedora, you can't build
> rustc. At minimum, you need a "stage0" compiler, which is an archived
> older rustc binary. (rustc originally bootstrapped with OCaml, but
> building the whole history of Rust from the OCaml days to present
> every time Fedora builds Firefox seems excessively impractical.)

Out of interest, would that actually involve building every single Linux 
snapshot from https://github.com/rust-lang/rust/blob/master/src/snapshots.txt 
in sequence? All 319 of them?

Thanks
Liam Wilson
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform