public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: c.christian.joensson@telia.com
To: gcc-gnats@gcc.gnu.org
Subject: target/9628: ICE in gcc 3.4 20030203 sparc{64,}-linux: bfd/linker.c:2738: internal compiler error: output_operand: invalid expression as operand
Date: Sat, 08 Feb 2003 17:16:00 -0000	[thread overview]
Message-ID: <20030208170643.12305.qmail@sources.redhat.com> (raw)


>Number:         9628
>Category:       target
>Synopsis:       ICE in gcc 3.4 20030203 sparc{64,}-linux: bfd/linker.c:2738: internal compiler error: output_operand: invalid expression as operand
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Feb 08 17:16:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     c.christian.joensson@telia.com
>Release:        3.4 (experimental) 20030203 -- 20030306
>Organization:
>Environment:
Aurora SPARC Linux on SS20 (sun4m) and U1 (sun4u)
>Description:
When trying to bootstrap/build gcc and binutils joined cvs trunks,
using a previous such build as bootstrap, I get an ICE...


chj@sparky:/usr/local/src/gcc-binutils/trunk/objdir/bfd$ gdb /usr/local/gcc-binutils/bin/gcc
GNU gdb Red Hat Linux (5.2-2)
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "sparc-redhat-linux"...
(gdb) set args -DHAVE_CONFIG_H -I. -I/usr/local/src/gcc-binutils/trunk/gcc-binutils/bfd -I. -D_GNU_SOURCE -I.
+-I/usr/local/src/gcc-binutils/trunk/gcc-binutils/bfd -I/usr/local/src/gcc-binutils/trunk/gcc-binutils/bfd/../include
+-I/usr/local/src/gcc-binutils/trunk/gcc-binutils/bfd/../intl -I../intl -W -Wall -Wstrict-prototypes -Wmissing-prototypes -g -O2+-c /usr/local/src/gcc-binutils/trunk/gcc-binutils/bfd/linker.c  -fPIC -DPIC -o .libs/linker.o
(gdb) r
Starting program: /usr/local/gcc-binutils/bin/gcc -DHAVE_CONFIG_H -I. -I/usr/local/src/gcc-binutils/trunk/gcc-binutils/bfd -I.
+-D_GNU_SOURCE -I. -I/usr/local/src/gcc-binutils/trunk/gcc-binutils/bfd
+-I/usr/local/src/gcc-binutils/trunk/gcc-binutils/bfd/../include -I/usr/local/src/gcc-binutils/trunk/gcc-binutils/bfd/../intl
+-I../intl -W -Wall -Wstrict-prototypes -Wmissing-prototypes -g -O2 -c
+/usr/local/src/gcc-binutils/trunk/gcc-binutils/bfd/linker.c  -fPIC -DPIC -o .libs/linker.o
/usr/local/src/gcc-binutils/trunk/gcc-binutils/bfd/linker.c: In function `default_data_link_order':
/usr/local/src/gcc-binutils/trunk/gcc-binutils/bfd/linker.c:2738: internal compiler error: output_operand: invalid expression as+operand
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.

Program exited with code 01.
(gdb) bt
No stack.
(gdb) q
>How-To-Repeat:
   well, compile bfd/linker.c using a recent binutils
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


                 reply	other threads:[~2003-02-08 17:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030208170643.12305.qmail@sources.redhat.com \
    --to=c.christian.joensson@telia.com \
    --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).