Comment 2 for bug 1094650

Hmm, v8 seems to have run into something similar, and they suggest changing the client code instead of silencing the warning. Unfortunately, the relevant client code is something we don't have much control over.

http://code.google.com/p/v8/issues/detail?id=2149

We might be able to work around it by putting the relevant sections in extern "C" blocks if this only happens when compiling C++