It's obvious that the function above is called by this one, and the exception
it throws cannot really propagate. The solution to this mystery is the fact
that msvc doesn't give a damn, and gcc does not either since OOo has used
-fno-enforce-sh-specs since 2001. But clang does, so fix this for now,
although it should possibly be just dumped.