However, it has not done so "on a regular basis" (to say otherwise is complete bullshit. I'm pretty sure the last major backwards incompatible change was version 3.0, which was 2 years ago). However, from where I sit, it's changed seriously less than asm.js in the past few years!
We'll see how long asm.js actually stays backwards compatible without having real impact.
'seriously less than asm.js in the past few years' is a blatantly fallacious claim. asm.js, as a spec, is barely a year old (going by the date of dherman's first public commit to his github repository) and the first implementation is younger than that. Mozilla turned the implementation around in a few months with a handful of engineers.
See, e.g., pcwalton's own comments:
"Most of the changes needed to fill in the few remaining holes in asm.js help everyone. SIMD and 64-bit integers, for example, are something the entire Web would benefit from, asm and non-asm writers alike."
Such changes would almost certainly be backwards incompatible with what exists now.
"'seriously less than asm.js in the past few years' is a blatantly fallacious claim."
Errr, given asm.js has changed a lot in the year it's been around, and LLVM has not changed in any backwards compatible way in that time period, it's actually what you would call "trivially true", not "blatantly false".
Again, asm.js has 'changed' but has not broken backwards compatibility, because it's just javascript and remains so.
You especially can't do this when the parent made the claim that PNaCL has exactly this issue.