FYI, the 3.5 merge is breaking on the bots and users are reporting errors as well. I'm not sure why it builds ok for me locally, but breaks elsewhere, yet. Anyhow, use incoming at your own risk for now - stick to master if you want something stable.
But help figuring out what is wrong on incoming is very welcome though! (More details in https://github.com/kripken/emscripten-fastcomp/issues/51 ) - Alon On Wed, Jan 7, 2015 at 1:10 PM, Alon Zakai <[email protected]> wrote: > The *master* branch was just merged to from incoming. This is after a long > break from merges, due to windows issues and end-of-year holiday timing. > The main big change is that master is now at 1.29.0 and includes the new > native optimizer being on by default. See the previous mailing list post on > the native optimizer for more details. > > The *incoming* branch was just merged to with LLVM 3.5, and bumped to > 1.29.1. This brings incoming up to date with the latest stable release of > LLVM and clang. There is at least one known issue, however, that breaks one > of the embind tests, due to a sophisticated usage of modern c++11 features > that are broken in latest clang + latest libc++ (see discussion in > https://github.com/kripken/emscripten-fastcomp/issues/51 ). Otherwise the > test suite passes locally. > > Please test one or both, and report any issues you find. > > - Alon > > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
