Issue 2512413002: Merged: Fix function name inference corruption for async functions

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Issue 2512413002: Merged: Fix function name inference corruption for async functions (Closed)

Created:
4 years, 1 month ago by Dan Ehrenberg

Modified:
4 years, 1 month ago

Reviewers:
gsathya

CC:
v8-reviews_googlegroups.com, v8-merges_googlegroups.com, ulan

Target Ref:
refs/pending/branch-heads/5.6

Project:
v8

Visibility:
Public.

Merged: Fix function name inference corruption for async functions Revision: 06f8e877267c9acae10e53e3054bea209dc92b78 BUG=chromium:658267 LOG=N NOTRY=true NOPRESUBMIT=true NOTREECHECKS=true R=gsathya@chromium.org Committed: https://chromium.googlesource.com/v8/v8/+/797c065a6fee9543920e9baab26887373e082c1d

Created: 4 years, 1 month ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+10 lines, -3 lines)			Patch
	M	src/parsing/func-name-inferrer.cc	View		1 chunk	+5 lines, -3 lines	0 comments	Download
	A	test/mjsunit/regress/regress-cr-658267.js	View		1 chunk	+5 lines, -0 lines	0 comments	Download

Total messages: 5 (1 generated)

Dan Ehrenberg

NOTE: This script will no longer automatically update include/v8-version.h and create a tag. This is ...

4 years, 1 month ago (2016-11-19 20:16:55 UTC) #2

Dan Ehrenberg

4 years, 1 month ago (2016-11-19 20:27:27 UTC) #5

Message was sent while issue was closed.

Committed patchset #1 (id:1) manually as
797c065a6fee9543920e9baab26887373e082c1d.