public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: java/6484: Error of compilation of GCJ-3.0 (debian gcj-3.0.4-5
Date: Sat, 27 Apr 2002 12:46:00 -0000	[thread overview]
Message-ID: <20020427194603.27983.qmail@sources.redhat.com> (raw)

The following reply was made to PR java/6484; it has been noted by GNATS.

From: Tom Tromey <tromey@redhat.com>
To: pierre.habouzit@m4x.org
Cc: gcc-gnats@gcc.gnu.org, debian-gcc@lists.debian.org
Subject: Re: java/6484: Error of compilation of GCJ-3.0 (debian gcj-3.0.4-5
Date: 27 Apr 2002 13:44:59 -0600

 >>>>> "Pierre" == pierre habouzit <pierre.habouzit@m4x.org> writes:
 
 Pierre> Synopsis:       Error of compilation of GCJ-3.0 (debian gcj-3.0.4-5
 Pierre> Release:        3.0.4 (Debian testing/unstable)
 
 Pierre> 	there is a bug when compiling this function: 
 Pierre> 	,-------------------------------------------------------
 Pierre> 	    void setInt(int newInt, int pos) {
 Pierre> 	        set[pos] = newInt;
 Pierre> 		for(int i=0; i<=pos; i++) ++sums[set[i]+newInt];
 Pierre> 	    }
 Pierre> 	`-------------------------------------------------------
 
 Could you be more specific?  What happens?  What did you expect to
 happen?
 
 When I compile this to bytecode with gcj3.1, the output is identical
 either way.  Are you compiling to object code?  What flags are you
 using?
 
 Can you send a complete short program that shows the exact problem?
 That would be most convenient.
 
 Thanks,
 Tom


             reply	other threads:[~2002-04-27 19:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-27 12:46 Tom Tromey [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-30 11:14 tromey
2002-04-27 15:16 Pierre Habouzit
2002-04-26 17:16 pierre.habouzit

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=20020427194603.27983.qmail@sources.redhat.com \
    --to=tromey@redhat.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    /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).