public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: jccosta@lucent.com
To: gcc-gnats@gcc.gnu.org
Subject: c++/4740: internal error
Date: Tue, 30 Oct 2001 04:56:00 -0000	[thread overview]
Message-ID: <20011030125517.1597.qmail@sourceware.cygnus.com> (raw)

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

>Number:         4740
>Category:       c++
>Synopsis:       internal error
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          ice-on-legal-code
>Submitter-Id:   net
>Arrival-Date:   Tue Oct 30 04:56:01 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     jccosta@lucent.com
>Release:        GCC 3.0 (not 3.0.1)
>Organization:
>Environment:
Conectiva 7.0 (i686-pc-linux-gnu/3.0), kernel: 2.2.19-15cl
>Description:
When I compile PWLIB system, during the release compilation results:

-------------------------------------------------------
g++ -Wall -DP_LINUX -D_REENTRANT -DP_HAS_SEMAPHORES -fPIC -DP_PTHREADS -DPBYTE_ORDER=PLITTLE_ENDIAN -I/home/jccosta/pwlib/include/ptlib/unix -DHAS_VIDEOCAPTURE -I/home/jccosta/pwlib/include -O3 -DNDEBUG  -c channel.cxx -o /home/jccosta/pwlib/lib/obj_linux_x86_r/channel.o
../common/pchannel.cxx: In static member function `static BOOL 
   PFile::Copy(const PFilePath&, const PFilePath&, int)':
../common/pchannel.cxx:950: Internal error: Falha de segmentação
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL: http://www.gnu.org/software/gcc/bugs.html > for instructions.
------------------------------------------------------
>How-To-Repeat:
Compile this code
>Fix:
Change the -O3 flag to -O2
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-10-30  4:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-30  4:56 jccosta [this message]
2001-10-31 20:46 rodrigc
2001-12-01  0:35 rodrigc
2001-12-01  0:46 rodrigc

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=20011030125517.1597.qmail@sourceware.cygnus.com \
    --to=jccosta@lucent.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).