Control flow in BasicMatcher::matches could be improved

Noticed that when running various benchmarks, e.g., Octane gbemu, in the presence of many compiler control directives that BasicMatcher::matches may show up prominently in some profiles.

During experiments it appears that on some platforms, Windows in particular, small adjustments to the control flow in that method - specifically to avoid eager lookup of Symbol*'s that won't be used - can have a significant impact.

This issue is possibly part of JDK-8057169