When finding renderers in the cache, the stride of the current vertex
buffer object is also taken into account.

This fixes a problem where a renderer could be used to draw a
vertex buffer object with a different stride value than the renderer
captured when the renderer was created.
Hide all of the console.* stuff behind a compile time flag
Merge pull request #962 from ehsan/openal

Hide all of the console.* stuff behind a compile time flag
add OPENAL_DEBUG to settings.js
Merge pull request #956 from michaeljbishop/fix-stride-discrepancy-in-renderer-cache

Finding a renderer in the cache now takes into account the current VBO stride.
add test for pull #956
fix asm*.test_cases
do not warn/error on unresolved symbols that have been declared dead
mark undefined symbol as dead in bullet
make Pointer_stringify argument handling consistent
fix printing of %llx very small and very large values
add more vsnprintf testing
switchify the main formatString loop
add option to turn all unresolved references into dead functions (i.e., no compile-time warnings or errors, instead runtime aborts
check for utf and avoid the overhead if not necessary; remove UTF_STRING_SUPPORT
fix bullet benchmark
process in chunks in fast path in Pointer_stringify
v1.3.1
Merge branch 'incoming' of https://github.com/kripken/emscripten into dataURL