- 23 Mar, 2015 1 commit
-
-
johan authored
as of https://reviews.freebsd.org/D848. This makes V8 build on FreeBSD-current (and the forthcoming 11). BUG=none LOG=n Review URL: https://codereview.chromium.org/1025823003 Cr-Commit-Position: refs/heads/master@{#27348}
-
- 20 Mar, 2015 23 commits
-
-
akos.palfi authored
Port d21fd154 TEST=mjsunit/harmony/reflect-construct BUG= Review URL: https://codereview.chromium.org/1022053002 Cr-Commit-Position: refs/heads/master@{#27347}
-
Toon Verwaest authored
BUG=chromium:469148 LOG=y R=dcarney@chromium.org Review URL: https://codereview.chromium.org/1023123003 Cr-Commit-Position: refs/heads/master@{#27346}
-
ishell authored
Revert of Allow compaction when incremental marking is on. (patchset #1 id:1 of https://codereview.chromium.org/1014263002/) Reason for revert: It seems to cause crbug/469146. Original issue's description: > Allow compaction when incremental marking is on. > > BUG=chromium:450824 > LOG=NO > > Committed: https://crrev.com/92f96e4e9a527fcb085b68f81ee14b26acdd4719 > Cr-Commit-Position: refs/heads/master@{#27267} TBR=hpayer@chromium.org,ulan@chromium.org NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=chromium:450824 Review URL: https://codereview.chromium.org/1026813002 Cr-Commit-Position: refs/heads/master@{#27345}
-
caitpotter88 authored
BUG=v8:3977 R=dslomov@chromium.org, arv@chromium.org LOG=N Review URL: https://codereview.chromium.org/1018043003 Cr-Commit-Position: refs/heads/master@{#27344}
-
balazs.kilvady authored
Port 3aa206b8 BUG=v8:3952 LOG=n Review URL: https://codereview.chromium.org/1020223002 Cr-Commit-Position: refs/heads/master@{#27343}
-
chunyang.dai authored
port 1382879f (r27016). oringinal commit message: [turbofan] Implement throwing exceptions into TurboFan code. This extends the stack unwinding logic to respect optimized frames and perform a lookup in the handler table to find handlers. It also contains fixes to the API call stubs to allow a stack walk while promoting scheduled exceptions. BUG= Review URL: https://codereview.chromium.org/1023943002 Cr-Commit-Position: refs/heads/master@{#27342}
-
bmeurer authored
R=jarin@chromium.org BUG=chromium:468162 LOG=y Review URL: https://codereview.chromium.org/1027753002 Cr-Commit-Position: refs/heads/master@{#27341}
-
yangguo authored
This speeds up multiple uses of the serializer quite a bit. R=mvstanton@chromium.org Review URL: https://codereview.chromium.org/1003363003 Cr-Commit-Position: refs/heads/master@{#27340}
-
rossberg authored
TBR=dslomov@chromium.org BUG= Review URL: https://codereview.chromium.org/1027693003 Cr-Commit-Position: refs/heads/master@{#27339}
-
rossberg authored
R=dslomov@chromium.org BUG=v8:3956 LOG=N Review URL: https://codereview.chromium.org/1021213002 Cr-Commit-Position: refs/heads/master@{#27338}
-
dslomov authored
String functions are shipping since 4.1/Chrome M41, it is time to unflag. R=yanngguo@chromium.org,rossberg@chromium.org BUG= Review URL: https://codereview.chromium.org/1024813002 Cr-Commit-Position: refs/heads/master@{#27337}
-
bmeurer authored
Turn Math.acos, Math.asin, Math.atan, Math.atan2, Math.sign and Math.trunc into inlinable builtins. R=yangguo@chromium.org BUG=v8:3952 LOG=n Review URL: https://codereview.chromium.org/1027713002 Cr-Commit-Position: refs/heads/master@{#27336}
-
jochen authored
Maybe it was overapproximated via the idle notification already, so just don't retry in that case BUG=chromium:469023 R=hpayer@chromium.org LOG=n Review URL: https://codereview.chromium.org/1025603003 Cr-Commit-Position: refs/heads/master@{#27335}
-
ulan authored
BUG=v8:3974 LOG=NO Review URL: https://codereview.chromium.org/1021523002 Cr-Commit-Position: refs/heads/master@{#27334}
-
bmeurer authored
BUG=chromium:469089 LOG=n R=jarin@chromium.org Review URL: https://codereview.chromium.org/1026683002 Cr-Commit-Position: refs/heads/master@{#27333}
-
chunyang.dai authored
port 2ecdf736 (r27014). original commit message: Fix exception for assignment to uninitialised const. BUG= Review URL: https://codereview.chromium.org/1028533002 Cr-Commit-Position: refs/heads/master@{#27332}
-
jarin authored
To ensure termination, we need to be sure that once we start weakening a node, we keep weakening that node in subsequent re-typings. Until now, we were guessing that we previously weakened from the type. This change introduces a set of nodes that have already be weakened, so that we have a reliable way to detect previous weakening. BUG=chromium:468799 LOG=n R=bmeurer@chromium.org Review URL: https://codereview.chromium.org/1019883002 Cr-Commit-Position: refs/heads/master@{#27331}
-
Benedikt Meurer authored
R=dcarney@chromium.org Review URL: https://codereview.chromium.org/1028563002 Cr-Commit-Position: refs/heads/master@{#27330}
-
Benedikt Meurer authored
R=dcarney@chromium.org, yangguo@chromium.org BUG=v8:3952 LOG=n Review URL: https://codereview.chromium.org/1021183002 Cr-Commit-Position: refs/heads/master@{#27329}
-
Benedikt Meurer authored
R=dcarney@chromium.org Review URL: https://codereview.chromium.org/1028553002 Cr-Commit-Position: refs/heads/master@{#27328}
-
v8-autoroll authored
Rolling v8/third_party/icu to d319ad9e25e8045f051dcd30bd5835f99936af6c TBR=machenbach@chromium.org Review URL: https://codereview.chromium.org/1021953002 Cr-Commit-Position: refs/heads/master@{#27327}
-
akos.palfi authored
Port d21fd154 Known issue: the mjsunit/harmony/reflect-construct test fails, it will be addressed in a follow-up CL. BUG= Review URL: https://codereview.chromium.org/1021863002 Cr-Commit-Position: refs/heads/master@{#27326}
-
aperez authored
The problem manifests itself when parsing manages to return something meaningful in the presence of a stack overflow. This happens because calling ParserBase::Next() will still return one valid token on stack overflow, before starting to return invalid tokens. Take the following input as example: a.map(v => v + 1); | | already next token parsed (which will be an invalid token (identifier) because of a stack overflow) The "v" may have been already parsed into a VariableProxy, then if a stack overflow occurs, next token will be an invalid token (instead of Token::ARROW), but the parser will return the VariableProxy. This always happens when lazy-parsing arrow functions, so the position in the input stream where the the arrow function code ends is known. This fix adds a check that ensures that parsing ended at the end position of the arrow function. BUG=465671 LOG=N Review URL: https://codereview.chromium.org/1023483003 Cr-Commit-Position: refs/heads/master@{#27325}
-
- 19 Mar, 2015 16 commits
-
-
verwaest authored
Cannot use Handle<T>::cast in Unique<T>::cast since it will try to do a T::cast (and its typecheck) concurrently, which is unsafe concurrently on moving values BUG= Review URL: https://codereview.chromium.org/1022943002 Cr-Commit-Position: refs/heads/master@{#27324}
-
hpayer authored
TBR=verwaest@chromium.org,ulan@chromium.org,ishell@chromium.org NOTRY=true Review URL: https://codereview.chromium.org/1027463002 Cr-Commit-Position: refs/heads/master@{#27323}
-
ulan authored
BUG=chromium:468749 LOG=NO TEST=Emscripten/NBodyJava Review URL: https://codereview.chromium.org/1014093005 Cr-Commit-Position: refs/heads/master@{#27322}
-
hpayer authored
Rename kMaxFrameRenderingIdleTime to kMaxActiveIdleTime and adjust it to the currently maximum value of 50ms passed in by the Blink scheduler. BUG=468692 LOG=n Review URL: https://codereview.chromium.org/1024543002 Cr-Commit-Position: refs/heads/master@{#27321}
-
rossberg authored
R=dslomov@chromium.org BUG=v8:3956 LOG=N Review URL: https://codereview.chromium.org/1019283002 Cr-Commit-Position: refs/heads/master@{#27320}
-
titzer authored
R=mstarzinger@chromium.org BUG= Review URL: https://codereview.chromium.org/1022783002 Cr-Commit-Position: refs/heads/master@{#27319}
-
jochen authored
With this patch, it'll look like this: $ out/x64.optdebug/d8 --expose-trigger-failure test/mjsunit/mjsunit.js test/mjsunit/verify-assert-false.js ==== C stack trace =============================== 1: V8_Fatal 2: v8::internal::FunctionCallbackArguments::Call(void (*)(v8::FunctionCallbackInfo<v8::Value> const&)) 3: 0x727ced 4: 0x72b6ba 5: 0x188c7f607f9b BUG=none R=svenpanne@chromium.org LOG=y Review URL: https://codereview.chromium.org/1018313003 Cr-Commit-Position: refs/heads/master@{#27318}
-
hpayer authored
BUG=468601 LOG=n Review URL: https://codereview.chromium.org/1016353002 Cr-Commit-Position: refs/heads/master@{#27317}
-
caitpotter88 authored
BUG=v8:3900 LOG=N R=dslomov@chromium.org Review URL: https://codereview.chromium.org/913073003 Cr-Commit-Position: refs/heads/master@{#27316}
-
weiliang.lin authored
BUG= Review URL: https://codereview.chromium.org/998883002 Cr-Commit-Position: refs/heads/master@{#27315}
-
ulan authored
BUG= Review URL: https://codereview.chromium.org/1009603003 Cr-Commit-Position: refs/heads/master@{#27314}
-
dslomov authored
Only adds a counter id, does not count anything. R=jochen@chromium.org BUG=v8:3942 LOG=N Review URL: https://codereview.chromium.org/1020883002 Cr-Commit-Position: refs/heads/master@{#27313}
-
yangguo authored
I was mistaken, cons strings only occur a lot for custom heap snapshots, not for the default start-up snapshot. R=erik.corry@gmail.com, mvstanton@chromium.org Review URL: https://codereview.chromium.org/1023673003 Cr-Commit-Position: refs/heads/master@{#27312}
-
rodolph.perfetta authored
BUG= Review URL: https://codereview.chromium.org/1020863003 Cr-Commit-Position: refs/heads/master@{#27311}
-
jarin authored
With this change, we remember the types of frame state inputs (in a new operator, called TypedStateValues). Instead of inferring the value types when building translations, we used the recorded types. The original approach was not reliable because the passes after simplified lowering can change node types, and this in turn confuses the translation builder. BUG=chromium:468727 LOG=n R=bmeurer@chromium.org Review URL: https://codereview.chromium.org/1015423002 Cr-Commit-Position: refs/heads/master@{#27310}
-
yangguo authored
R=verwaest@chromium.org Review URL: https://codereview.chromium.org/1025433002 Cr-Commit-Position: refs/heads/master@{#27309}
-