Fix bug in date code where -0 was not mapped to 0. This caused the ...

test/mjsunit/date.js

 // Copyright 2008 the V8 project authors. All rights reserved.
 // Redistribution and use in source and binary forms, with or without
 // modification, are permitted provided that the following conditions are
 // met:
 //
 //     * Redistributions of source code must retain the above copyright
 //       notice, this list of conditions and the following disclaimer.
 //     * Redistributions in binary form must reproduce the above
 //       copyright notice, this list of conditions and the following
 //       disclaimer in the documentation and/or other materials provided
@@ skipping 136 matching lines @@
 // Test that toLocaleTimeString only returns the time portion of the
 // date without the timezone information.
 function testToLocaleTimeString() {
   var d = new Date();
   var s = d.toLocaleTimeString();
   assertEquals(8, s.length);
 }
 
 testToLocaleTimeString();
 
+// Test that -0 is treated correctly in MakeDay.
+var d = new Date();
+assertDoesNotThrow("d.setDate(-0)");
+assertDoesNotThrow("new Date(-0, -0, -0, -0, -0, -0. -0)");

[Erik Corry, 2010/07/02 19:59:47]

Perhaps we should also pass 0x40000000 and -0x40000001 to check that almost-Smis
work.

[Mads Ager (chromium), 2010/07/02 20:07:07]

Done.

+
 
 // Modified test from WebKit
 // LayoutTests/fast/js/script-tests/date-utc-timeclip.js:
 
 assertEquals(Date.UTC(275760, 8, 12, 23, 59, 59, 999), 8639999999999999);
 assertEquals(Date.UTC(275760, 8, 13), 8640000000000000);
 assertTrue(isNaN(Date.UTC(275760, 8, 13, 0, 0, 0, 1)));
 assertTrue(isNaN(Date.UTC(275760, 8, 14)));
 
 assertEquals(Date.UTC(-271821, 3, 20, 0, 0, 0, 1), -8639999999999999);
 assertEquals(Date.UTC(-271821, 3, 20), -8640000000000000);
 assertTrue(isNaN(Date.UTC(-271821, 3, 19, 23, 59, 59, 999)));
 assertTrue(isNaN(Date.UTC(-271821, 3, 19)));