From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <java-prs-return-2779-listarch-java-prs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 27142 invoked by alias); 7 May 2004 05:09:48 -0000
Mailing-List: contact java-prs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:java-prs-subscribe@gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/java-prs/>
List-Post: <mailto:java-prs@gcc.gnu.org>
List-Help: <mailto:java-prs-help@gcc.gnu.org>, <http://gcc.gnu.org/ml/#faqs>
Sender: java-prs-owner@gcc.gnu.org
Received: (qmail 27090 invoked by uid 48); 7 May 2004 05:09:47 -0000
Date: Fri, 07 May 2004 05:09:00 -0000
From: "jlquinn at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Message-ID: <20040507050940.15336.jlquinn@gcc.gnu.org>
Reply-To: gcc-bugzilla@gcc.gnu.org
Subject: [Bug libgcj/15336] New: SimpleTimeZone.getOffset assumes same mode as rules
X-Bugzilla-Reason: CC
X-SW-Source: 2004-q2/txt/msg00085.txt.bz2
List-Id: <java-prs.sourceware.org>

The code currently assumes that the same mode is used on the call to getOffset
as was used to create the start or end rule being compared to.  This bug is a
placeholder as I'm planning to fix this as part of hacking SimpleTimeZone.

The fix I'm planning will convert rules and offset queries to absolute time so
they can be compared safely.

I think 8321 will be fixed by this as well.

-- 
           Summary: SimpleTimeZone.getOffset assumes same mode as rules
           Product: gcc
           Version: 3.5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: libgcj
        AssignedTo: jlquinn at gcc dot gnu dot org
        ReportedBy: jlquinn at gcc dot gnu dot org
                CC: gcc-bugs at gcc dot gnu dot org,java-prs at gcc dot gnu
                    dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15336