On 2014-02-26, 8:44 AM, Nicholas Nethercote wrote:
On Tue, Feb 25, 2014 at 8:18 PM, Mike Hommey <m...@glandium.org> wrote:
I never understood why we need those jobs to be builds. Why not turn
--enable-valgrind on m-c builds, and run valgrind as a test job?
--disable-jemalloc is needed as well.
That shouldn't be needed anymore with --soname-synonyms=somalloc=NONE
on the valgrind command line.
I did not know about that! Thank you. I filed
https://bugzilla.mozilla.org/show_bug.cgi?id=977067 to update |mach
valgrind-test| accordingly, and I will also update the docs.
That will make it easier to use standard builds... turning on
--enable-valgrind for m-c builds is pretty reasonable, because it
makes only tiny differences (insertion of a few nops in
non-perf-critical places) to the resulting code.
Sorry if this is driving the thread off-topic, but can you please
provide a list of the things that --enable-valgrind changes? I am very
curious to know the implications of turning this on.
Thanks!
Ehsan
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
