public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Mathieu Imrazene"<imrazene@nortelnetworks.com>
To: gcc@gcc.gnu.org
Subject: GCC3.0.4 : Solaris 2.6 build failure
Date: Fri, 22 Feb 2002 07:09:00 -0000	[thread overview]
Message-ID: <3C765A57.5A9210C0@europem01.nt.com> (raw)


/var/tmp/build_gcc/gcc/xgcc -B/var/tmp/build_gcc/gcc/
-B/home/imrazene/gcc-3.0.4/sparc-sun-solaris2.6/bin/
-B/home/imrazene/gcc-3.0.4/sparc-sun-solaris2.6/lib/ -isystem
/home/imrazene/gcc-3.0.4/sparc-sun-solaris2.6/include -DHAVE_CONFIG_H
-I. -I/var/tmp/gcc-3.0.4/libjava
-I./include -I/var/tmp/gcc-3.0.4/libjava -Iinclude
-I/var/tmp/gcc-3.0.4/libjava/include
-I/var/tmp/gcc-3.0.4/libjava/../boehm-gc -I./../boehm-gc
-DSOLARIS_THREADS=1
-D_SOLARIS_PTHREADS=1 -DSILENT=1 -DNO_SIGNALS=1 -DJAVA_FINALIZATION=1
-DGC_GCJ_SUPPORT=1 -I/var/tmp/gcc-3.0.4/libjava/libltdl
-I/var/tmp/gcc-3.0.4/libjava/libltdl
-I/var/tmp/gcc-3.0.4/libjava/.././libjava/../gcc
-I/var/tmp/gcc-3.0.4/libjava/../zlib
-I/var/tmp/gcc-3.0.4/libjava/../libffi/include -I../libffi/include -W
-Wall -g
-O2 -c /var/tmp/gcc-3.0.4/libjava/java/lang/k_tan.c  -fPIC -DPIC -o
java/lang/.libs/k_tan.o
/var/tmp/gcc-3.0.4/libjava/java/lang/k_tan.c: In function
`__kernel_tan':
/var/tmp/gcc-3.0.4/libjava/java/lang/k_tan.c:130: Insn does not satisfy
its constraints:
(insn 611 521 342 (set (reg:DI 34 %f2)
        (reg/v:DI 64 %f32 [245])) 58 {*movdi_insn_sp32} (nil)
    (nil))
/var/tmp/gcc-3.0.4/libjava/java/lang/k_tan.c:130: Internal compiler
error in reload_cse_simplify_operands, at reload1.c:8364
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
gmake[2]: *** [java/lang/k_tan.lo] Error 1
gmake[2]: Leaving directory
`/var/tmp/build_gcc/sparc-sun-solaris2.6/libjava'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory
`/var/tmp/build_gcc/sparc-sun-solaris2.6/libjava'
gmake: *** [all-target-libjava] Error 2

config.status contains :
# This directory was configured as follows:
/var/tmp/gcc-3.0.4/configure
--with-gcc-version-trigger=/var/tmp/gcc-3.0.4/gcc/version.c
--host=sparc-sun-solaris2.6 --prefix=/home/imrazene/gcc-3.0.4
--with-gnu-as
--with-gnu-ld --with-as=/home/imrazene/bin/as
--with-ld=/home/imrazene/bin/ld --with-cpu=ultrasparc
--enable-threads=posix --enable-languages=c,c++,java --norecursion
# using "mh-frag"


--
Mathieu Imrazene

========================================================
Il ne faut pas confondre 'vitesse' et 'precipitation'...



             reply	other threads:[~2002-02-22 14:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-22  7:09 Mathieu Imrazene [this message]
2002-02-22 13:28 ` Alexandre Oliva
2002-02-22 13:46   ` Jakub Jelinek
2002-02-22 13:51     ` Alexandre Oliva
2002-02-22 13:55       ` Jakub Jelinek
2002-02-22 14:27         ` Alexandre Oliva
2002-02-22 14:28           ` Jakub Jelinek
2002-02-22 15:30             ` Alexandre Oliva
2002-02-22 16:00               ` Craig Rodrigues
2002-02-22 19:56 lucier
2002-02-23  2:54 ` Jakub Jelinek

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=3C765A57.5A9210C0@europem01.nt.com \
    --to=imrazene@nortelnetworks.com \
    --cc=gcc@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).