[Bug libgcj/19649] java.util.Date.getTimezoneOffset returns negated output

-- What|Removed |Added Target Milestone|--- |4.0.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19649

[Bug libgcj/19649] java.util.Date.getTimezoneOffset returns negated output

--- Additional Comments From mckinlay at redhat dot com 2005-01-29 00:45 --- Fixed -- What|Removed |Added Status|NEW |RESOLVED R

[Bug libgcj/19649] java.util.Date.getTimezoneOffset returns negated output

--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-01-29 00:44 --- Subject: Bug 19649 CVSROOT:/cvs/gcc Module name:gcc Changes by: [EMAIL PROTECTED] 2005-01-29 00:43:51 Modified files: libjava: ChangeLog libjava/java/util:

[Bug libgcj/19649] java.util.Date.getTimezoneOffset returns negated output

--- Additional Comments From mckinlay at redhat dot com 2005-01-29 00:37 --- Turns out its already fixed in GNU Classpath. Re-syncing with their version. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19649

[Bug libgcj/19649] java.util.Date.getTimezoneOffset returns negated output

--- Additional Comments From mckinlay at redhat dot com 2005-01-29 00:30 --- I've put a test case for this in mauve: gnu/testlet/java/util/Date/getTimezoneOffset.java This test case also exposes some problems with libgcj's underlying TimeZone data. This patch looks correct, though.

[Bug libgcj/19649] java.util.Date.getTimezoneOffset returns negated output

-- What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed||1 Last reconfirmed|-00-00 00:00:00 |2005-01-

[Bug libgcj/19649] java.util.Date.getTimezoneOffset returns negated output

--- Additional Comments From walters at redhat dot com 2005-01-28 20:16 --- Yeah, I'm almost positive it's the cause. At least I narrowed down this behavior difference in JDK versus gcj, but it's possible there's another bug in there. Is the test suite patch for mauve? I think they'd

[Bug libgcj/19649] java.util.Date.getTimezoneOffset returns negated output

--- Additional Comments From marco at gnome dot org 2005-01-28 17:35 --- Colin, is this one the cause of the setTimeStamp/getTimeStamp mismatch with postgre jdbc? I have a testcase for that one in case it's of any use... -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19649

[Bug libgcj/19649] java.util.Date.getTimezoneOffset returns negated output

-- What|Removed |Added OtherBugsDependingO||16990 nThis|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19649

[Bug libgcj/19649] java.util.Date.getTimezoneOffset returns negated output

-- What|Removed |Added Component|java|libgcj http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19649