Issue 228103002: Revert "Handlify deoptimization data allocators."

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 228103002: Revert "Handlify deoptimization data allocators." (Closed)

Created:
6 years, 8 months ago by Sven Panne

Modified:
6 years, 8 months ago

Reviewers:
Michael Starzinger

CC:
v8-dev

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

Visibility:
Public.

Revert "Handlify deoptimization data allocators." This reverts r20552, it breaks with snapshot=off. TBR=mstarzinger@chromium.org BUG=cctest/test-lockers/ExtensionsRegistration LOG=n Committed: https://code.google.com/p/v8/source/detail?r=20556

Created: 6 years, 8 months ago

Download [raw] [tar.bz2]

	Unified diffs	Side-by-side diffs	Stats (+88 lines, -18 lines)			Patch
M	src/factory.h	View	3 chunks	+3 lines, -5 lines	0 comments	Download
M	src/factory.cc	View	5 chunks	+32 lines, -9 lines	0 comments	Download
M	src/heap.h	View	1 chunk	+6 lines, -0 lines	0 comments	Download
M	src/heap.cc	View	2 chunks	+16 lines, -1 line	0 comments	Download
M	src/objects.h	View	3 chunks	+13 lines, -3 lines	0 comments	Download
M	src/objects.cc	View	1 chunk	+18 lines, -0 lines	0 comments	Download

Total messages: 2 (0 generated)

Sven Panne

Committed patchset #1 manually as r20556 (tree was closed).

6 years, 8 months ago (2014-04-08 06:15:33 UTC) #1

Michael Starzinger

6 years, 8 months ago (2014-04-08 08:02:01 UTC) #2

Message was sent while issue was closed.

Thanks for taking care of this. Will look into it.