Issue 568743003: Fixpoint typing has to consider all imprecise nodes

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 568743003: Fixpoint typing has to consider all imprecise nodes (Closed)

Created:
6 years, 3 months ago by rossberg

Modified:
6 years, 3 months ago

Reviewers:
Jarin

CC:
v8-dev

Base URL:
https://v8.googlecode.com/svn/branches/bleeding_edge

Project:
v8

Visibility:
Public.

Fixpoint typing has to consider all imprecise nodes R=jarin@chromium.org BUG= Committed: https://code.google.com/p/v8/source/detail?r=23931

Created: 6 years, 3 months ago

Download [raw] [tar.bz2]

	Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+13 lines, -45 lines)			Patch
M	src/compiler/typer.cc	View	1	2 chunks	+13 lines, -5 lines	0 comments	Download
M	test/cctest/cctest.status	View	1	1 chunk	+0 lines, -30 lines	0 comments	Download
M	test/mjsunit/mjsunit.status	View	1	2 chunks	+0 lines, -5 lines	0 comments	Download
M	test/webkit/webkit.status	View	1	1 chunk	+0 lines, -5 lines	0 comments	Download

Total messages: 3 (0 generated)

Jarin

lgtm. Could you possibly enable the tests that it fixes? (in mjsunit.status)

6 years, 3 months ago (2014-09-12 13:59:30 UTC) #2

Message was sent while issue was closed.

Committed patchset #2 manually as 23931.