Issue 18418003: Use stored Isolate pointer instead of Isolate::Current()

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 18418003: Use stored Isolate pointer instead of Isolate::Current() (Closed)

Created:
7 years, 5 months ago by yurys

Modified:
7 years, 5 months ago

Reviewers:
loislo, Jakob Kummerow

CC:
v8-dev, alph

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

Visibility:
Public.

Use stored Isolate pointer instead of Isolate::Current() Fixed a couple of places where stored pointer to the isolate can be used instead of reading from thread local storage. BUG=None R=jkummerow@chromium.org Committed: https://code.google.com/p/v8/source/detail?r=15457

Created: 7 years, 5 months ago

Download [raw] [tar.bz2]

	Unified diffs	Side-by-side diffs	Stats (+6 lines, -7 lines)			Patch
M	src/cpu-profiler.h	View	1 chunk	+1 line, -1 line	0 comments	Download
M	src/cpu-profiler.cc	View	2 chunks	+2 lines, -3 lines	0 comments	Download
M	src/log.cc	View	3 chunks	+3 lines, -3 lines	0 comments	Download

Total messages: 3 (0 generated)

yurys

7 years, 5 months ago (2013-07-02 15:44:38 UTC) #3

Message was sent while issue was closed.

Committed patchset #1 manually as r15457 (presubmit successful).