public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Matt Welsh <mdw@cs.berkeley.edu>
To: Warren Levy <warrenl@cygnus.com>
Cc: Tom Tromey <tromey@cygnus.com>, java-discuss@sourceware.cygnus.com
Subject: Re: BigInteger compile fails
Date: Sat, 01 Apr 2000 00:00:00 -0000	[thread overview]
Message-ID: <200002152340.PAA14884@mnemosyne.CS.Berkeley.EDU> (raw)
In-Reply-To: <Pine.SOL.3.91.1000215152335.10850A-100000@fencer.cygnus.com>

Just to follow up on this - everything seems to work fine with the 
latest egcs from CVS. 

Cheers -
Matt Welsh

Warren Levy <warrenl@cygnus.com> writes:
> On Mon, 14 Feb 2000, Matt Welsh wrote:
> 
> > > Either the latest egcs, or 2.95.2 with Bryce's compatibility patch.
> > 
> > I was using Bryce's patch. There must be something else wrong with 2.95.2
> > then?
> 
> There's an easy workaround in the BigInteger source code.  If you can't find 
> the right compiler fix, go ahead and apply this in the meantime.
> --warrenl
> 
> 
> --- BigInteger.java	Mon Feb 14 02:01:31 2000
> +++ BigInteger.java.workaround	Tue Feb 15 15:29:14 2000
> @@ -279,7 +279,10 @@ public class BigInteger extends Number i
>  
>    private final boolean isNegative()
>    {
> -    return (words == null ? ival : words[ival - 1]) < 0;
> +    // FIXME: compiler error in egcs-19991214 when compiling to bytecode (on
> ly).
> +    // return (words == null ? ival : words[ival - 1]) < 0;
> +    int tmp = (words == null ? ival : words[ival - 1]);
> +    return tmp < 0;
>    }
>  
>    public int signum()

  reply	other threads:[~2000-04-01  0:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-01  0:00 Matt Welsh
2000-04-01  0:00 ` Per Bothner
2000-04-01  0:00 ` Tom Tromey
2000-04-01  0:00   ` Matt Welsh
2000-04-01  0:00     ` Warren Levy
2000-04-01  0:00       ` Matt Welsh [this message]
2000-04-01  0:00     ` Tom Tromey

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=200002152340.PAA14884@mnemosyne.CS.Berkeley.EDU \
    --to=mdw@cs.berkeley.edu \
    --cc=java-discuss@sourceware.cygnus.com \
    --cc=tromey@cygnus.com \
    --cc=warrenl@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).