public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: green@cygnus.com
To: java-gnats@sourceware.cygnus.com
Subject: libgcj/1195: Primes.java gives bad results.
Date: Wed, 20 Dec 2000 12:21:00 -0000	[thread overview]
Message-ID: <19990809063614.18599.qmail@egcs.cygnus.com> (raw)

>Number:         1195
>Category:       libgcj
>Synopsis:       Primes.java gives bad results.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    tromey
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Dec 20 12:17:22 PST 2000
>Closed-Date:    Wed Aug 11 14:31:23 PDT 1999
>Last-Modified:  Wed Aug 11 14:31:23 PDT 1999
>Originator:     Anthony Green
>Release:        2.95
>Organization:
>Environment:
Debian Linux 2.1, x86
>Description:
libgcj/libjava/testsuite/libjava.lang/Primes.java is failing.
My guess is that it represents a failure in BitSet, which
is uses quite heavily.
>How-To-Repeat:
Run libgcj/libjava/testsuite/libjava.lang/Primes.java
(or `make check')
>Fix:
This is a bit-shifting overflow in BitSet.java (the "1" 
constants are treated as int by default and need to be 
explicitly specified as long). Patch posted to java-patches
and committed.
>Release-Note:

>Audit-Trail:

Formerly PR libgcj/23

State-Changed-From-To: open->feedback
State-Changed-By: bryce
State-Changed-When: Wed Aug 11 02:44:59 1999
State-Changed-Why:
    Suggested fix posted to java-patches.
State-Changed-From-To: feedback->closed
State-Changed-By: bryce
State-Changed-When: Wed Aug 11 14:31:23 1999
State-Changed-Why:
    fix checked-in to cvs
>Unformatted:



                 reply	other threads:[~2000-12-20 12:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=19990809063614.18599.qmail@egcs.cygnus.com \
    --to=green@cygnus.com \
    --cc=java-gnats@sourceware.cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).