public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: shibuya@bu-denken.co.jp
To: gcc-gnats@gcc.gnu.org
Subject: c/10058: gcc is crashed on compiling gcc
Date: Thu, 13 Mar 2003 09:46:00 -0000	[thread overview]
Message-ID: <20030313093843.15842.qmail@sources.redhat.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1725 bytes --]


>Number:         10058
>Category:       c
>Synopsis:       gcc is crashed on compiling gcc
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Mar 13 09:46:01 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     SHIBUYA Katsutoshi
>Release:        3.2.2
>Organization:
>Environment:

>Description:
I'm creating a cross-compiler for arm-linux target on darwin (MacOSX) using gcc-3.2.2
I compiled and installed gcc-3.2.2 for darwin as follows;

% mkdir build_gcc_darwin
% cd build_gcc_darwin
% ../gcc-3.2.2/configure
% make
% sudo make install

Then I compiled cross-compiler as follows;

% mkdir build_gcc_arm
% cd build_gcc_arm
% ../gcc-3.2.2/configure --target=arm-linux --prefix=$HOME/work/Armadillo/darwin --with-local-prefix=$HOME/work/Armadillo --enable-languages=c,c++ --disable-libgcj
% make

And after compiling some codes the gcc crashed saying;

gcc -DIN_GCC -DCROSS_COMPILE   -g -O2 -W -Wall -Wwrite-strings -Wstrict-prototyp
es -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long  -DHAVE_CONFIG_H 
   -I. -I. -I../../gcc-3.2.2/gcc -I../../gcc-3.2.2/gcc/. -I../../gcc-3.2.2/gcc/c
onfig -I../../gcc-3.2.2/gcc/../include -c insn-extract.c ¥
  -o insn-extract.o
gcc: Internal error: Illegal instruction (program cc1)
Please submit a full bug report.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
make[1]: *** [insn-extract.o] Error 1
make: *** [all-gcc] Error 2

I reproduced it many times so it does not look like a hardware trouble.
What additional information can I send you?
>How-To-Repeat:

>Fix:

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


                 reply	other threads:[~2003-03-13  9:46 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=20030313093843.15842.qmail@sources.redhat.com \
    --to=shibuya@bu-denken.co.jp \
    --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).