Bug 875656 - IonMonkey: Juggle registers around to reduce the number of temporaries needed by LConcat. r=bhackett
bug 883350: move SDK_HEADERS to mozbuild r=mshal
Bug 900683 - IonMonkey: Register allocation niceties. r=bhackett
Bug 900683 - IonMonkey: Make the backtracking allocator remember spill intervals so that it doesn't create redundant spill intervals. r=bhackett
Bug 917991 - Use higher-level MacroAssembler interfaces in a few more places. r=luke
Bug 917991 - Note a non-trivial implicit coupling. r=luke
Bug 915765 - fix -Wformat warnings in xpcom/; r=bsmedberg

Unfortunately this doesn't fix all platforms, since Android's inttypes.h doesn't
have the right macros for intptr_t at least, but it makes the situation a little
better.
Bug 919672 - lower the suspect referent count for the observer service's memory reporter; r=njn,wchen

I have a couple score (hundreds?) of open tabs and have been noticing of late
that the observer service has 4k+ observers for such a session.  I was a bit
surprised by this, and lowered the suspect referent count a bit to see if I
could determine what was going on.

There's nothing particularly unusual with my setup, but I'd like to propose
that the count be lowered somewhat anyway.  I think it's useful for about:memory
to provide as much information as possible about what might be going on.  I've
also tried to update the explanatory text to indicate that merely having high
counts is not necessarily symptomatic of a leak.
Bug 916923 - work around crash reporter issues with adjacent memory mappings on x86 android; r=glandium,f=gbrown
Bug 918934 - Update jit-tests remote harness; r=terrence
Bug 918392 - Handle symlinked directories properly; r=glandium
Backed out changeset dec7ac293e74 (bug 782546) for breaking the test it was trying to annotate.