public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Matthias Klose <doko@smile.cs.tu-berlin.de>
To: gcc-gnats@gcc.gnu.org, debian-gcc@lists.debian.org
Subject: target/9201: [3.2 branch regression] ICE compiling octave-2.1 on m68k-linux
Date: Mon, 06 Jan 2003 20:06:00 -0000	[thread overview]
Message-ID: <E18VdPz-0006J6-00@smile.cs.tu-berlin.de> (raw)


>Number:         9201
>Category:       target
>Synopsis:       [3.2 branch regression] ICE compiling octave-2.1 on m68k-linux
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          ice-on-legal-code
>Submitter-Id:   net
>Arrival-Date:   Mon Jan 06 12:06:03 PST 2003
>Closed-Date:
>Last-Modified:
>Originator:     Dirk Eddelbuettel <edd@debian.org>
>Release:        3.2.1 (Debian) (Debian unstable)
>Organization:
The Debian Project
>Environment:
System: Debian GNU/Linux (unstable)
Architecture: m68k
>Description:
[ Reported to the Debian BTS as report #175478.
  Please CC 175478@bugs.debian.org on replies.
  Log of report can be found at http://bugs.debian.org/175478 ]
	

gcc version 3.2.2 20021231 (Debian prerelease)

the file compiles without -fPIC. 2.95 and 3.0 compile the file.

$ /usr/bin/g77-3.2 -c -fPIC -O0 -g0 zbknu.f
zbknu.f: In subroutine `zbknu': 
zbknu.f:567: Internal compiler error in instantiate_virtual_regs_1, at function.c:3980 
Please submit a full bug report, 
with preprocessed source if appropriate. 
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. 

[attching file in a followup]

>How-To-Repeat:
	
>Fix:
	
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2003-01-06 20:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-06 20:06 Matthias Klose [this message]
2003-05-10  1:06 Dara Hazeghi

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=E18VdPz-0006J6-00@smile.cs.tu-berlin.de \
    --to=doko@smile.cs.tu-berlin.de \
    --cc=175478@bugs.debian.org \
    --cc=debian-gcc@lists.debian.org \
    --cc=gcc-gnats@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).