Revert of [regexp] Support unicode capture names in non-unicode patterns

Revert of [regexp] Support unicode capture names in non-unicode patterns (patchset #3 id:40001 of https://codereview.chromium.org/2791163003/ )

Reason for revert:
The decision for the specification was to not have this syntax, and instead the syntax before this patch.

Original issue's description:
> [regexp] Support unicode capture names in non-unicode patterns
> 
> This ensures that capture names containing surrogate pairs are parsed
> correctly even in non-unicode RegExp patterns by introducing a new
> scanning mode which unconditionally combines surrogate pairs.
> 
> BUG=v8:5437, v8:6192
> 
> Review-Url: https://codereview.chromium.org/2791163003
> Cr-Commit-Position: refs/heads/master@{#44466}
> Committed: https://chromium.googlesource.com/v8/v8/+/a8651c5671dd6e41595ffb438e7ea013082f2d38

R=yangguo@chromium.org,jgruber@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=v8:5437, v8:6192
Review-Url: https://codereview.chromium.org/2859933003
Cr-Commit-Position: refs/heads/master@{#45088}
Committed: https://chromium.googlesource.com/v8/v8/+/f918404590b6800c5a5ef26fb358abbc28622deb

[Dan Ehrenberg, 2017-05-04 09:12:40]

Created Revert of [regexp] Support unicode capture names in non-unicode patterns

[Dan Ehrenberg, 2017-05-04 09:12:53]

Description was changed from

==========
Revert of [regexp] Support unicode capture names in non-unicode patterns
(patchset #3 id:40001 of https://codereview.chromium.org/2791163003/ )

Reason for revert:
The decision for the specification was to not have this syntax, and instead the
syntax before this patch.

Original issue's description:
> [regexp] Support unicode capture names in non-unicode patterns
> 
> This ensures that capture names containing surrogate pairs are parsed
> correctly even in non-unicode RegExp patterns by introducing a new
> scanning mode which unconditionally combines surrogate pairs.
> 
> BUG=v8:5437,v8:6192
> 
> Review-Url: https://codereview.chromium.org/2791163003
> Cr-Commit-Position: refs/heads/master@{#44466}
> Committed:
https://chromium.googlesource.com/v8/v8/+/a8651c5671dd6e41595ffb438e7ea013082...

TBR=yangguo@chromium.org,jgruber@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=v8:5437,v8:6192
==========

to

==========
Revert of [regexp] Support unicode capture names in non-unicode patterns
(patchset #3 id:40001 of https://codereview.chromium.org/2791163003/ )

Reason for revert:
The decision for the specification was to not have this syntax, and instead the
syntax before this patch.

Original issue's description:
> [regexp] Support unicode capture names in non-unicode patterns
> 
> This ensures that capture names containing surrogate pairs are parsed
> correctly even in non-unicode RegExp patterns by introducing a new
> scanning mode which unconditionally combines surrogate pairs.
> 
> BUG=v8:5437,v8:6192
> 
> Review-Url: https://codereview.chromium.org/2791163003
> Cr-Commit-Position: refs/heads/master@{#44466}
> Committed:
https://chromium.googlesource.com/v8/v8/+/a8651c5671dd6e41595ffb438e7ea013082...

R=yangguo@chromium.org,jgruber@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=v8:5437,v8:6192
==========

[Dan Ehrenberg, 2017-05-04 09:13:02]

The CQ bit was checked by littledan@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-05-04 09:13:08]

Dry run: CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-05-04 09:16:44]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-05-04 09:16:45]

Dry run: Try jobs failed on following builders:
  v8_linux_dbg_ng on master.tryserver.v8 (JOB_FAILED,
http://build.chromium.org/p/tryserver.v8/builders/v8_linux_dbg_ng/builds/25435)
  v8_linux_gcc_compile_rel on master.tryserver.v8 (JOB_FAILED,
http://build.chromium.org/p/tryserver.v8/builders/v8_linux_gcc_compile_rel/bu...)
  v8_mac_rel_ng on master.tryserver.v8 (JOB_FAILED,
http://build.chromium.org/p/tryserver.v8/builders/v8_mac_rel_ng/builds/21972)

[Dan Ehrenberg, 2017-05-04 09:59:25]

The CQ bit was checked by littledan@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-05-04 09:59:33]

Dry run: CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-05-04 10:20:12]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-05-04 10:20:14]

Dry run: Try jobs failed on following builders:
  v8_linux64_verify_csa_rel_ng on master.tryserver.v8 (JOB_FAILED,
http://build.chromium.org/p/tryserver.v8/builders/v8_linux64_verify_csa_rel_n...)
  v8_linux64_verify_csa_rel_ng_triggered on master.tryserver.v8 (JOB_FAILED,
http://build.chromium.org/p/tryserver.v8/builders/v8_linux64_verify_csa_rel_n...)

[Dan Ehrenberg, 2017-05-04 10:36:56]

The CQ bit was checked by littledan@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-05-04 10:37:03]

Dry run: CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[Dan Ehrenberg, 2017-05-04 11:07:07]

Just to be sure, does it seem like a good plan to revert this patch?

[commit-bot: I haz the power, 2017-05-04 11:08:12]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-05-04 11:08:13]

Dry run: This issue passed the CQ dry run.

[jgruber, 2017-05-04 11:11:19]

On 2017/05/04 11:07:07, Dan Ehrenberg wrote:
> Just to be sure, does it seem like a good plan to revert this patch?

Yes, SGTM. We got lucky in that the patch handles exactly the problem case in
isolation. For future reference, the discussion triggering this change is at
https://github.com/tc39/test262/pull/998.

[jgruber, 2017-05-04 11:11:35]

On 2017/05/04 11:11:19, jgruber wrote:
> On 2017/05/04 11:07:07, Dan Ehrenberg wrote:
> > Just to be sure, does it seem like a good plan to revert this patch?
> 
> Yes, SGTM. We got lucky in that the patch handles exactly the problem case in
> isolation. For future reference, the discussion triggering this change is at
> https://github.com/tc39/test262/pull/998.

And LGTM

[Dan Ehrenberg, 2017-05-04 12:07:09]

The CQ bit was checked by littledan@chromium.org

[commit-bot: I haz the power, 2017-05-04 12:07:15]

CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-05-04 12:33:39]

CQ is committing da patch.

Bot data: {"patchset_id": 120001, "attempt_start_ts": 1493899629475770,
"parent_rev": "6b4e8c2114b04d3d9f39f4d7c49108ea4d56ae12", "commit_rev":
"f918404590b6800c5a5ef26fb358abbc28622deb"}

[commit-bot: I haz the power, 2017-05-04 12:33:46]

Description was changed from

==========
Revert of [regexp] Support unicode capture names in non-unicode patterns
(patchset #3 id:40001 of https://codereview.chromium.org/2791163003/ )

Reason for revert:
The decision for the specification was to not have this syntax, and instead the
syntax before this patch.

Original issue's description:
> [regexp] Support unicode capture names in non-unicode patterns
> 
> This ensures that capture names containing surrogate pairs are parsed
> correctly even in non-unicode RegExp patterns by introducing a new
> scanning mode which unconditionally combines surrogate pairs.
> 
> BUG=v8:5437,v8:6192
> 
> Review-Url: https://codereview.chromium.org/2791163003
> Cr-Commit-Position: refs/heads/master@{#44466}
> Committed:
https://chromium.googlesource.com/v8/v8/+/a8651c5671dd6e41595ffb438e7ea013082...

R=yangguo@chromium.org,jgruber@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=v8:5437,v8:6192
==========

to

==========
Revert of [regexp] Support unicode capture names in non-unicode patterns
(patchset #3 id:40001 of https://codereview.chromium.org/2791163003/ )

Reason for revert:
The decision for the specification was to not have this syntax, and instead the
syntax before this patch.

Original issue's description:
> [regexp] Support unicode capture names in non-unicode patterns
> 
> This ensures that capture names containing surrogate pairs are parsed
> correctly even in non-unicode RegExp patterns by introducing a new
> scanning mode which unconditionally combines surrogate pairs.
> 
> BUG=v8:5437,v8:6192
> 
> Review-Url: https://codereview.chromium.org/2791163003
> Cr-Commit-Position: refs/heads/master@{#44466}
> Committed:
https://chromium.googlesource.com/v8/v8/+/a8651c5671dd6e41595ffb438e7ea013082...

R=yangguo@chromium.org,jgruber@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=v8:5437,v8:6192

Review-Url: https://codereview.chromium.org/2859933003
Cr-Commit-Position: refs/heads/master@{#45088}
Committed:
https://chromium.googlesource.com/v8/v8/+/f918404590b6800c5a5ef26fb358abbc286...
==========

[commit-bot: I haz the power, 2017-05-04 12:33:46]

Committed patchset #3 (id:120001) as
https://chromium.googlesource.com/v8/v8/+/f918404590b6800c5a5ef26fb358abbc286...