public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: derek@mangrocks.com
To: gcc-gnats@gcc.gnu.org
Subject: other/6947: /usr/software/gcc/gcc-3.1/gcc/libgcc2.c:64: internal error: Segmentation fault
Date: Thu, 06 Jun 2002 09:06:00 -0000	[thread overview]
Message-ID: <20020606155754.15026.qmail@sources.redhat.com> (raw)


>Number:         6947
>Category:       other
>Synopsis:       /usr/software/gcc/gcc-3.1/gcc/libgcc2.c:64: internal error: Segmentation fault
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Jun 06 09:06:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Derek Whitten
>Release:        unknown-1.0
>Organization:
>Environment:
OpenBSD 3.1 (GENERIC) #59: Sat Apr 13 15:28:52 MDT 2002

    deraadt@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC

cpu0: Intel Pentium III (Coppermine) ("GenuineIntel" 686-class, 128KB L2 cache)

cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SYS,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SIMD

real mem  = 268005376 (261724K)

avail mem = 242712576 (237024K)

>Description:
/usr/software/gcc/gcc-3.1/gcc/libgcc2.c:64: 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.

gmake[2]: *** [libgcc/./_negdi2.o] Error 1

gmake[2]: Leaving directory `/usr/software/gcc/gcc-3.1/objdir/gcc'

gmake[1]: *** [stmp-multilib] Error 2

gmake[1]: Leaving directory `/usr/software/gcc/gcc-3.1/objdir/gcc'

gmake: *** [all-gcc] Error 2



**********



compile options:



bash-2.05a# /usr/software/gcc/gcc-3.1/configure  --with-gnu-as --enable-checking



bash-2.05a# gmake 



*** other ***



bash-2.05a# gmake -v

GNU Make version 3.79.1, by Richard Stallman and Roland McGrath.

Built for i386-unknown-openbsd3.1



*** note ****



I am not exactly sure on what files that you would require to work on this.. I was RTFM @ http://www.gnu.org/software/gcc/bugs.html#need

and could not locate any files with the extension of .i or .ii.  I will keep all of this intact and can/will provide files at request ( i don't believe that a tarball of the whole dir would be appropriate ) -- email me with files required and i will make them available.



Thanks for all the hard work and killer software  :P



Derek Whitten



>How-To-Repeat:

>Fix:

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


                 reply	other threads:[~2002-06-06 16:06 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=20020606155754.15026.qmail@sources.redhat.com \
    --to=derek@mangrocks.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).