- 20 Jun, 2017 1 commit
-
-
Daniel Ehrenberg authored
Previously, Date.toString() and friends were completely implementation-defined. However, they actually seemed to match each other's behavior with the exception of how years less than 1000 are formatted. The rough consensus among browsers seemed to be %04d, so this was standardized at TC39 [1]. V8 previously used %4d (it was the only one to do so); this patch adopts the new standard. [1] https://github.com/tc39/ecma262/commit/5d4acf3377e1b0ad4a4660c57108db1b28ef20ff Bug: v8:6076 Change-Id: I8c795a4e1b71187ad7c24a1aee8d7d66719a2586 Reviewed-on: https://chromium-review.googlesource.com/536733 Commit-Queue: Daniel Ehrenberg <littledan@chromium.org> Reviewed-by: Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#46037}
-
- 16 Feb, 2017 1 commit
-
-
littledan authored
ES2016 changed the default timezone of dates to be conditional on whether a time is included. The semantics were a compromise approach based on web compatibility feedback from V8, but until now, we have been shipping ES5.1 default timezone semantics. This patch implements the new semantics, following ChakraCore and SpiderMonkey (though JSC implements V8's previous semantics). BUG=chromium:589858 Review-Url: https://codereview.chromium.org/2648603002 Cr-Commit-Position: refs/heads/master@{#43239}
-
- 12 Jan, 2016 1 commit
-
-
bmeurer authored
This migrates the remaining Date builtins to C++ and removes obsolete intrinsics and JavaScript wrappers. This reduces the overhead imposed by the Date builtins, and will allow us to optimize them later in the TurboFan compiler, while the interpreter doesn't need to worry about them. R=yangguo@chromium.org BUG=chromium:576574 LOG=n Committed: https://crrev.com/1e51af1a5c80b1650de47dd4bc8f846fa2d85281 Cr-Commit-Position: refs/heads/master@{#33228} Review URL: https://codereview.chromium.org/1579613002 Cr-Commit-Position: refs/heads/master@{#33231}
-
- 08 Jan, 2016 1 commit
-
-
bmeurer authored
There's no reason to have JavaScript wrappers for those accessors, since the meat is already in hand-written native code (via %_DateField). First step now to put them into native builtins. Next step will be to completely remove %_DateField. R=yangguo@chromium.org Review URL: https://codereview.chromium.org/1567353002 Cr-Commit-Position: refs/heads/master@{#33172}
-
- 15 Oct, 2015 1 commit
-
-
ulan authored
Revert of Make dates default to the local timezone if none specified (https://codereview.chromium.org/1229903004/) Even though the change is ES6 spec compliant, we decided to revert to be consistent with other browsers and work on fixing the spec. Original issue's description: > Make dates default to the local timezone if none specified > > In ES5, dates were supposed to default to UTC if no timezone was specified. However, this changed in ES6, which specified that dates should be in the local timezone if no timezone was specified. This CL updates our behavior to match that part of the ES6 spec. > BUG=chromium:391730, v8:4242 > LOG=Y > Committed: https://crrev.com/f06754a8e1d305a43560705f6c167d85d40e602d > Cr-Commit-Position: refs/heads/master@{#29854} BUG=chromium:543320,chromium:539813 LOG=NO Review URL: https://codereview.chromium.org/1403153003 Cr-Commit-Position: refs/heads/master@{#31295}
-
- 31 Aug, 2015 1 commit
-
-
littledan authored
This is a change for ES2015. Date objects have mutable state, so having a mutable prototype is bad for SES requirements, and it is an inconsistency from the typical ES2015 class style of objects BUG=v8:4004 LOG=Y R=adamk Review URL: https://codereview.chromium.org/1317403002 Cr-Commit-Position: refs/heads/master@{#30486}
-
- 24 Jul, 2015 1 commit
-
-
hichris123 authored
In ES5, dates were supposed to default to UTC if no timezone was specified. However, this changed in ES6, which specified that dates should be in the local timezone if no timezone was specified. This CL updates our behavior to match that part of the ES6 spec. BUG=chromium:391730, v8:4242 LOG=Y Review URL: https://codereview.chromium.org/1229903004 Cr-Commit-Position: refs/heads/master@{#29854}
-
- 23 Jun, 2015 2 commits
-
-
arv authored
We used to call toString as a method which is not safe. BUG=v8:4225 LOG=Y R=adamk, littledan CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_chromium_rel_ng;tryserver.blink:linux_blink_rel Review URL: https://codereview.chromium.org/1200033003 Cr-Commit-Position: refs/heads/master@{#29242}
-
mathias authored
TEST=mjsunit/date BUG=v8:4226 LOG=N Review URL: https://codereview.chromium.org/1203733002 Cr-Commit-Position: refs/heads/master@{#29240}
-
- 22 Jul, 2013 1 commit
-
-
yangguo@chromium.org authored
R=mvstanton@chromium.org BUG= Review URL: https://codereview.chromium.org/19807002 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@15793 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 03 Jul, 2013 1 commit
-
-
jkummerow@chromium.org authored
BUG=v8:2745 R=jkummerow@chromium.org Review URL: https://codereview.chromium.org/18187006 Patch from Jochen Eisinger <jochen@chromium.org>. git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@15479 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 10 Sep, 2012 1 commit
-
-
yangguo@chromium.org authored
BUG= Review URL: https://chromiumcodereview.appspot.com/10915062 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@12471 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 09 Mar, 2012 1 commit
-
-
ulan@chromium.org authored
R=mstarzinger@chromium.org BUG= TEST= Review URL: https://chromiumcodereview.appspot.com/9652030 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10987 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 31 Oct, 2011 1 commit
-
-
mstarzinger@chromium.org authored
R=yangguo@chromium.org BUG=v8:1792 TEST=mjsunit/date Review URL: http://codereview.chromium.org/8423004 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9842 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 28 Oct, 2011 1 commit
-
-
mstarzinger@chromium.org authored
This fixes Date.prototyoe.toISOString to throw a RangeError exception for invalid time values. It also includes a fix to removes the arbitrary (and completely bogus) range limit on the date value during construction of a Date object. Note that we still have bogus range limits on the year and month values. R=lrn@chromium.org BUG=v8:1792 TEST=mjsunit/date,test262/15.9.5.43-0-* Review URL: http://codereview.chromium.org/8392036 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9829 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 01 Jul, 2011 1 commit
-
-
lrn@chromium.org authored
This means that ES5 Date Time Strings will default to UTC if timezone is absent. Handle as many legacy strings as possible the same way as before BUG=v8:1498 TEST=mjsunit/date Review URL: http://codereview.chromium.org/7291022 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@8513 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 16 Dec, 2010 1 commit
-
-
ager@chromium.org authored
methods rely on the time values passed in being within a certain range - not significantly larger than the the ECMA 262 specified time range. When creating a time, always make it NaN if there is no way that it can be within range even after UTC conversion. Review URL: http://codereview.chromium.org/5905003 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@6048 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 02 Jul, 2010 1 commit
-
-
ager@chromium.org authored
runtime system to throw an exception because it expected smi arguments. Review URL: http://codereview.chromium.org/2848038 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@5013 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 23 Mar, 2010 2 commits
-
-
oleg@chromium.org authored
Review URL: http://codereview.chromium.org/1084018 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@4236 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
http://code.google.com/p/v8/issues/detail?id=659oleg@chromium.org authored
Fix bug http://code.google.com/p/v8/issues/detail?id=659. Move the limits check for date before the time zone offset is applied. Review URL: http://codereview.chromium.org/1075016 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@4232 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 03 Mar, 2010 1 commit
-
-
oleg@chromium.org authored
Review URL: http://codereview.chromium.org/661466 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@4009 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 16 Feb, 2009 1 commit
-
-
lrn@chromium.org authored
git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1276 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 09 Sep, 2008 1 commit
-
-
christian.plesner.hansen@gmail.com authored
Added presubmit step to check copyright. git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@242 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 04 Sep, 2008 1 commit
-
-
ager@chromium.org authored
only return the time portion of the date. git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@128 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 22 Aug, 2008 1 commit
-
-
christian.plesner.hansen authored
In the shell sample don't print the result of executing a script, only evaluating expressions. Fixed issue when building samples on Windows using a shared V8 library. Added visibility option on Linux build which makes the generated library 18% smaller. Changed build system to accept multiple build modes in one build and generate seperate objects, libraries and executables for each mode. Removed deferred negation optimization (a * -b => -(a * b)) since this visibly changes operand conversion order. Improved parsing performance by introducing stack guard in preparsing. Without a stack guard preparsing always bails out with stack overflow. git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@16 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-