public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "tg at mirbsd dot org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/57929] New: gcc-4.8: FTBFS on m68k: ICE compiling libjava/interpret.cc
Date: Thu, 18 Jul 2013 19:22:00 -0000	[thread overview]
Message-ID: <bug-57929-8172@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 57929
           Summary: gcc-4.8: FTBFS on m68k: ICE compiling
                    libjava/interpret.cc
           Product: gcc
           Version: 4.8.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: java
          Assignee: unassigned at gcc dot gnu.org
          Reporter: tg at mirbsd dot org

Created attachment 30525
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30525&action=edit
original preprocessed source code

Hi,

this is a forward for http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711558
which is an ICE trying to bootstrap gcj-4.8 that I *think* remember seeing for
gcj-4.7 (but not gcj-4.6 which works fine) already too, on the Debian/m68k
Linux 3.x (NPTL, atomics via syscall) platform.

The problem is now that the gcj part got merged into the main gcc source
package and this is kinda holding up our entire toolchain update (also, I think
gcj-4.6 got removed from sid).

Since I was unable to get OpenJDK/zero working either, gcj is our only hope to
keep Linux/m68k spinning so I’m hoping that $skilled_people will have a look at
it.

Preprocessed source attached here, too (xz compressed, hope that’s ok).
>From java-prs-return-11583-listarch-java-prs=gcc.gnu.org@gcc.gnu.org Fri Jul 19 09:52:33 2013
Return-Path: <java-prs-return-11583-listarch-java-prs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-java-prs@gcc.gnu.org
Received: (qmail 6522 invoked by alias); 19 Jul 2013 09:52:33 -0000
Mailing-List: contact java-prs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <java-prs.gcc.gnu.org>
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
Delivered-To: mailing list java-prs@gcc.gnu.org
Received: (qmail 6495 invoked by uid 48); 19 Jul 2013 09:52:32 -0000
From: "mikpe at it dot uu.se" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/57929] gcc-4.8: FTBFS on m68k: ICE compiling
 libjava/interpret.cc
Date: Fri, 19 Jul 2013 09:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: java
X-Bugzilla-Version: 4.8.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mikpe at it dot uu.se
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-57929-8172-v7StuOqAd7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-57929-8172@http.gcc.gnu.org/bugzilla/>
References: <bug-57929-8172@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2013-q3/txt/msg00002.txt.bz2
Content-length: 176

http://gcc.gnu.org/bugzilla/show_bug.cgi?idW929

--- Comment #1 from Mikael Pettersson <mikpe at it dot uu.se> ---
Dup of PR49847.  The patch attached there fixes this ICE.


             reply	other threads:[~2013-07-18 19:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-18 19:22 tg at mirbsd dot org [this message]
2013-07-19 11:03 ` [Bug java/57929] " tg at mirbsd dot de
2013-07-19 13:23 ` schwab@linux-m68k.org

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=bug-57929-8172@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=java-prs@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).