public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Daniel Bonniot <Daniel.Bonniot@inria.fr>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: java/4914: Internal compiler error in emit_move_insn, at expr.c:2713
Date: Sun, 12 Jan 2003 09:36:00 -0000	[thread overview]
Message-ID: <20030112093602.18465.qmail@sources.redhat.com> (raw)

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

>From Daniel.Bonniot@inria.fr  Mon Jan 13 01:03:45 2003
From: Daniel Bonniot <Daniel.Bonniot@inria.fr>
To: gcc-gnats@gcc.gnu.org,  gcc-prs@gcc.gnu.org,  gcc-bugs@gcc.gnu.org, 
 nobody@gcc.gnu.org,  java-prs@gcc.gnu.org
Cc:  
Subject: Re: java/4914: Internal compiler error in emit_move_insn, at expr.c:2713
Date: Sun, 12 Jan 2003 11:33:36 +0100

 This is a multi-part message in MIME format.
 --------------030305080104090104040108
 Content-Type: text/plain; charset=us-ascii; format=flowed
 Content-Transfer-Encoding: 7bit
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=4914
 
 I have a shorter test case that reproduces this bug (see the 
 attachement). The bug is still there as of gcj 3.2.1 (the location of 
 the internal compiler error is now expr.c:2769).
 
 It seems that the implementation of either 'swap' or 'dup_x1' is bogus. 
 This is a stopper for my using gcj at the moment. Can anybody help?
 
 Daniel
 
 
 --------------030305080104090104040108
 Content-Type: application/x-java-vm;
  name="fun.class"
 Content-Transfer-Encoding: base64
 Content-Disposition: inline;
  filename="fun.class"
 
 yv66vgADAC0AGQEAEGphdmEvbGFuZy9PYmplY3QHAAEBAAY8aW5pdD4BAAMoKVYMAAMABAoA
 AgAFAQAPamF2YS9sYW5nL0Zsb2F0BwAHAQAEKEYpVgwAAwAJCgAIAAoBAAdidWcvZnVuBwAM
 AQAEbWFpbgEABENvZGUBABJMb2NhbFZhcmlhYmxlVGFibGUBAAJmMAEAAUYBAAFmAQARTGph
 dmEvbGFuZy9GbG9hdDsBAA9MaW5lTnVtYmVyVGFibGUBAAR0eXBlAQAKU291cmNlRmlsZQEA
 BS4vYnVnACEADQACAAAAAAACAAkADgAJAAIADwAAADUAAwACAAAACyK7AAhaX7cAC0yxAAAA
 AgAQAAAADAABAAAACgARABIAAAAVAAAABgABAAAABQAWAAAAIShuaWNlLmxhbmcuZmxvYXQp
 LT5uaWNlLmxhbmcudm9pZAABAAMABAABAA8AAAARAAEAAQAAAAUqtwAGsQAAAAAAAQAXAAAA
 AgAY
 --------------030305080104090104040108--
 


             reply	other threads:[~2003-01-12  9:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-12  9:36 Daniel Bonniot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-12 19:15 Dara Hazeghi
2003-01-12 20:06 Jeff Sturm
2001-12-18 16:06 Tom Tromey
2001-11-15 12:41 Daniel.Bonniot

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=20030112093602.18465.qmail@sources.redhat.com \
    --to=daniel.bonniot@inria.fr \
    --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).