Fastcomp (the new llvm backend) now passes the expected part of the test
suite, and almost all fuzzing as well (except for issues due to
legalization in the pnacl passes we are using, which need more
investigation). So it is important to start getting testing done. This
command will run all the tests that should pass

EMCC_FAST_COMPILER=1 ./tests/runner.py default asm1 asm2

An issue we will start to have is bisecting regressions across two repos,
the emscripten one and the fastcomp one (or potentially worse, three if we
need to bisect the clang repo as well, but it is unmodified by us). Any
ideas on the best practices for something like that?

Looks like git submodules do not automatically bisect into them,
http://marc.info/?l=git&m=127609545324378&w=2 which would have seemed the
natural approach.

If there isn't a better idea, we could have the main repo always have an
explicit changeset of the other repo that it is expected to work with, in a
file, and we could write a script to bisect in tandem. I'm hoping there is
a better way though?

- 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/groups/opt_out.

Reply via email to