[turbofan] Remove unused constructor function matching from typer.

[turbofan] Remove unused constructor function matching from typer.

This optimization never triggers currently, and is inherently native
context dependent for no real reason (for example it will not properly
detect those constructors in the case of cross native context inlining),
plus it is slow and awkward.  In case we really need this functionality
at some point, we should find a way to make it work with the builtin
function id mechanism that is already in place to match other builtins.

R=jarin@chromium.org,rossberg@chromium.org

Committed: https://crrev.com/722e2e2b36d9add4b63cc70b108b735a28192354
Cr-Commit-Position: refs/heads/master@{#29365}

[Benedikt Meurer, 2015-06-30 03:50:31]

Hey Jaro,

This code is awkward and inherently native context dependent, plus we don't need
it (at least for now). I confirmed that we never hit this by adding CHECK(false)
to the branch and running test suites and benchmarks. I think the correct way to
deal with constructors on the global object is to either have them recognized
with builtin function id or via special global load support (which I'm working
on now), or both.

Please take a look.

Thanks,
Benedikt

Andreas: FYI

[Jarin, 2015-06-30 07:33:02]

lgtm

[Benedikt Meurer, 2015-06-30 07:33:38]

The CQ bit was checked by bmeurer@chromium.org

[commit-bot: I haz the power, 2015-06-30 07:33:48]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1221683006/1

[commit-bot: I haz the power, 2015-06-30 07:36:20]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-06-30 07:36:35]

Patchset 1 (id:??) landed as
https://crrev.com/722e2e2b36d9add4b63cc70b108b735a28192354
Cr-Commit-Position: refs/heads/master@{#29365}