public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Craig Metz <cmetz@inner.net>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: c/914
Date: Tue, 29 May 2001 17:56:00 -0000	[thread overview]
Message-ID: <20010530005601.13098.qmail@sourceware.cygnus.com> (raw)

The following reply was made to PR c/914; it has been noted by GNATS.

From: Craig Metz <cmetz@inner.net>
To: jsm28@gcc.gnu.org
Cc: gcc-gnats@gcc.gnu.org, jsm28@cam.ac.uk
Subject: Re: c/914 
Date: Tue, 29 May 2001 16:53:14 -0400

 In message <20010528114046.24428.qmail@sourceware.cygnus.com>, you write:
 >Synopsis: libgcc2 compile causes internal error for mips-wrs-vxworks
 >
 >State-Changed-From-To: open->feedback
 >State-Changed-By: jsm28
 >State-Changed-When: Mon May 28 04:40:45 2001
 >State-Changed-Why:
 >    Does this problem still occur with current 3.0 branch CVS?
 >
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=914&database=gcc
 
   First, I get:
 
 /usr/src/cvs/gcc-3.0/gcc/gcc/xgcc -B/usr/src/cvs/gcc-3.0/gcc/gcc/ -B/usr/local/mips-wrs-vxworks/mips-wrs-vxworks/bin/ -B/usr/local/mips-wrs-vxworks/mips-wrs-vxworks/lib/ -isystem /usr/local/mips-wrs-vxworks/mips-wrs-vxworks/include -O2  -DCROSS_COMPILE -DIN_GCC    -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -isystem ./include  -G 0 -g1 -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc -I. -I. -I. -I./. -I./config -I./../include  -DL_fixunsdfsi -c ./libgcc2.c -o  libgcc/./_fixunsdfsi.o
 In file included from /usr/local/mips-wrs-vxworks/mips-wrs-vxworks/include/types/vxArch.h:71,
                  from /usr/local/mips-wrs-vxworks/mips-wrs-vxworks/include/types/vxANSI.h:45,
                  from /usr/local/mips-wrs-vxworks/mips-wrs-vxworks/include/limits.h:24,
                  from /usr/src/cvs/gcc-3.0/gcc/gcc/include/limits.h:130,
                  from /usr/src/cvs/gcc-3.0/gcc/gcc/include/syslimits.h:7,
                  from /usr/src/cvs/gcc-3.0/gcc/gcc/include/limits.h:11,
                  from libgcc2.c:1166:
 /usr/src/cvs/gcc-3.0/gcc/gcc/include/arch/mips/archMips.h:42:19: r4000.h: No such file or directory
 make[2]: *** [libgcc/./_fixunsdfsi.o] Error 1
 make[2]: Leaving directory `/home/src/cvs/gcc-3.0/gcc/gcc'
 make[1]: *** [stmp-multilib] Error 2
 make[1]: Leaving directory `/home/src/cvs/gcc-3.0/gcc/gcc'
 make: *** [all-gcc] Error 2
 
   Dropping r400.h into the gcc build tree where fixincludes seems to have put
 archMips allows me to continue. Then, I get:
 
 /usr/src/cvs/gcc-3.0/gcc/gcc/xgcc -B/usr/src/cvs/gcc-3.0/gcc/gcc/ -B/usr/local/mips-wrs-vxworks/mips-wrs-vxwo
 rks/mips-wrs-vxworks/lib/ -isystem /usr/local/mips-wrs-vxworks/mips-wrs-vxworks/include -O2  -DCROSS_COMPILE 
 s -Wstrict-prototypes -Wmissing-prototypes -isystem ./include  -G 0 -g1 -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 -D__
  -I. -I. -I. -I./. -I./config -I./../include -fexceptions -c ./unwind-dw2.c -o libgcc/./unwind-dw2.o
 In file included from unwind-dw2.c:25:
 unwind-pe.h: In function `size_of_encoded_value':
 unwind-pe.h:68: warning: implicit declaration of function `abort'
 In file included from gthr-default.h:1,
                  from gthr.h:98,
                  from unwind-dw2.c:27:
 gthr-vxworks.h: In function `__gthread_once':
 gthr-vxworks.h:217: warning: unused parameter `once'
 gthr-vxworks.h: In function `__ehdtor':
 gthr-vxworks.h:232: warning: implicit declaration of function `taskVarGet'
 gthr-vxworks.h:237: warning: implicit declaration of function `taskVarSet'
 gthr-vxworks.h: In function `__gthread_key_create':
 gthr-vxworks.h:251: warning: implicit declaration of function `taskVarInit'
 gthr-vxworks.h:256: warning: implicit declaration of function `taskDeleteHookAdd'
 gthr-vxworks.h:244: warning: unused parameter `dtor'
 unwind-dw2.c: In function `extract_cie_info':
 unwind-dw2.c:219: warning: implicit declaration of function `strlen'
 unwind-dw2.c: In function `execute_stack_op':
 unwind-dw2.c:300: warning: `result' might be used uninitialized in this function
 unwind-dw2.c: In function `execute_cfa_program':
 unwind-dw2.c:775: warning: implicit declaration of function `alloca'
 unwind-dw2.c: In function `uw_frame_state_for':
 unwind-dw2.c:886: warning: implicit declaration of function `memset'
 unwind-dw2.c: In function `uw_install_context_1':
 unwind-dw2.c:1103: warning: implicit declaration of function `memcpy'
 unwind-dw2.c: At top level:
 unwind-dw2.c:1123: Internal error: Segmentation fault
 Please submit a full bug report,
 with preprocessed source if appropriate.
 See <URL: http://www.gnu.org/software/gcc/bugs.html > for instructions.
 make[2]: *** [libgcc/./unwind-dw2.o] Error 1
 make[2]: Leaving directory `/home/src/cvs/gcc-3.0/gcc/gcc'
 make[1]: *** [stmp-multilib] Error 2
 make[1]: Leaving directory `/home/src/cvs/gcc-3.0/gcc/gcc'
 make: *** [all-gcc] Error 2
 
   So it looks like things are not good. This is a checkout of a few minutes ago
 along the 3.0 branch.
 
                                                                         -Craig


             reply	other threads:[~2001-05-29 17:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-29 17:56 Craig Metz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-05-29 18:16 c/914 jsm28
2001-05-29 18:06 c/914 Craig Metz
2001-05-28  4:46 c/914 jsm28

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=20010530005601.13098.qmail@sourceware.cygnus.com \
    --to=cmetz@inner.net \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).