public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Robin Kirkham <Robin.Kirkham@mlb.dmt.csiro.au>
To: egcs@cygnus.com
Subject: 971122 for arm-coff dies building newlib/libm: testcase attached
Date: Wed, 26 Nov 1997 23:40:00 -0000	[thread overview]
Message-ID: <19971127064525.24524.qmail@ragnarok.mlb.dmt.csiro.au> (raw)

It's possible this is not a configuration that is supposed to work--I was 
just trying this out to prove a point but it backfired a little 8-(

I am not in a position to investigate it much, but I will report the problem
in case anyone is interested in or working on ARM support in egcs.

I built binutils 2.8.1 and egcs 971122 with target configuration arm-coff
(strictly, arm-1-coff) on a sun-sparc-solaris2.5.1 host. The tools and compiler
build without incident, including the gcclib and libstdc++ libraries. Then 
I configured newlib 1.8.0 similarly and started building it. The compiler
failed compiling newlib/libm/math/ef_exp.c. The error was

[much deleted ...]
arm-1-gcc -g -O2  -O2 -DABORT_PROVIDED -fno-builtin 
-I/opt/embedded/src/newlib-1.8.0/build-arm-1-coff/arm-1-coff/newlib/./targ-incl
ude -I/opt/embedded/src/newlib-1.8.0/newlib/./libc/include -c
../../../../../newlib/libm/math/ef_exp.c
../../../../../newlib/libm/math/ef_exp.c: In function `__ieee754_expf':
../../../../../newlib/libm/math/ef_exp.c:102: internal error--unrecognizable 
insn:
(insn 621 66 77 (set (reg:SF 49)
        (if_then_else:SF (eq (reg:CC 24 cc)
                (const_int 0))
            (reg/v:SF 31)
            (const_double:SF (cc0) 0 0))) -1 (insn_list 66 (nil))
    (expr_list:REG_DEAD (reg:CC 24 cc)
        (expr_list:REG_DEAD (reg/v:SF 31)
            (nil))))
arm-1-gcc: Internal compiler error: program cc1 got fatal signal 6
gmake[3]: *** [ef_exp.o] Error 1
gmake[3]: Leaving directory
`/opt/embedded/src/newlib-1.8.0/build-arm-1-coff/arm-1-coff/newlib/libm/math'


I've prepared a single file testcase bad.c (simply using arm-1-gcc -E) which
is attached to this mail. It causes a similar error (below). The compile 
succeeds if you don't use -O.

% arm-gcc -O -c bad.c    
ef_exp.c: In function `__ieee754_expf':
ef_exp.c:102: internal error--unrecognizable insn:

(insn 593 589 77 (set (reg:SF 46)
        (if_then_else:SF (eq (reg:CC 24 cc)
                (const_int 0))
            (reg/v:SF 31)
            (const_double:SF (cc0) 0 0))) -1 (insn_list 66 (nil))
    (expr_list:REG_DEAD (reg:CC 24 cc)
        (expr_list:REG_DEAD (reg/v:SF 31)
            (nil))))
arm-1-gcc: Internal compiler error: program cc1 got fatal signal 6
%

As I say I am not in a position to investigate this, but of course I'll
any addition information if someone wants.

Thanks,

Robin Kirkham			CSIRO Manufacturing Science and Technology
Project Engineer		Locked Bag 9, Preston 3072, Australia
robin.kirkham@mlb.dmt.csiro.au	Phone: +61 3 9662-7756  Fax: +61 3 9662-7851

             reply	other threads:[~1997-11-26 23:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-11-26 23:40 Robin Kirkham [this message]
1997-11-27  4:34 ` Richard Earnshaw
1997-11-27  8:38   ` Jeffrey A Law
     [not found] <199711281251.MAA19730@sun52.NIS.cambridge>
1997-12-01 19:30 ` Robin Kirkham

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=19971127064525.24524.qmail@ragnarok.mlb.dmt.csiro.au \
    --to=robin.kirkham@mlb.dmt.csiro.au \
    --cc=egcs@cygnus.com \
    /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).