public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janis at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/24605] [4.0/4.1 Regression] internal compiler error: Segmentation fault while compiling c++ file
Date: Sat, 05 Nov 2005 01:00:00 -0000	[thread overview]
Message-ID: <20051105010008.28879.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24605-7023@http.gcc.gnu.org/bugzilla/>

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



------- Comment #5 from janis at gcc dot gnu dot org  2005-11-05 01:00 -------
I tried out a few cross compilers for i686-pc-cygwin over the last few
months.  The code compiled cleanly on 20040607.  Sometime between then
and 20040709 it started failing with a different ICE from what it gets now.
For awhile (at least from 20040921-20051127) it got only:

C:/rah/Vc/CppLib/RefCntUtil.h:119: error: declaration of
`RefCntUtil::ucPtr<T>::operator T*() const'
C:/rah/Vc/CppLib/RefCntUtil.h:101: error: conflicts with previous declaration
`RefCntUtil::ucPtr<T>::operator X*() const'

That error went away.  The current ICE and several of the other errors started
sometime between 20050227-20050404.  Here's a testcase for one of them:

class CloneableObject
{
  friend class CloneWalker;
public:
  virtual void WalkClone(CloneWalker&) const = 0;
};

class CloneWalker
{
  CloneWalker(int) {}
  CloneWalker(void) {}
};

It fails on powerpc-linux with "error: ‘CloneWalker’ has not been declared",
the first error that the large testcase gets, not the one that leads to
the ICE.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24605


  parent reply	other threads:[~2005-11-05  1:00 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-01  1:01 [Bug c++/24605] New: " ron_hylton at hotmail dot com
2005-11-01  1:04 ` [Bug c++/24605] " ron_hylton at hotmail dot com
2005-11-01  1:10 ` [Bug c++/24605] [4.1 Regression] " pinskia at gcc dot gnu dot org
2005-11-01 15:29 ` [Bug c++/24605] [4.0/4.1 " pinskia at gcc dot gnu dot org
2005-11-03  6:42 ` mmitchel at gcc dot gnu dot org
2005-11-03 16:00 ` ron_hylton at hotmail dot com
2005-11-05  1:00 ` janis at gcc dot gnu dot org [this message]
2005-11-05  1:31 ` janis at gcc dot gnu dot org
2005-11-05 18:49 ` ron_hylton at hotmail dot com
2005-11-05 18:51 ` ron_hylton at hotmail dot com
2005-11-10 21:22 ` janis at gcc dot gnu dot org
2005-11-12  0:11 ` ron_hylton at hotmail dot com
2005-11-19  1:37 ` mmitchel at gcc dot gnu dot org
2006-02-14 18:11 ` [Bug c++/24605] [4.0/4.1/4.2 " amylaar at gcc dot gnu dot org
2006-02-14 18:15 ` amylaar at gcc dot gnu dot org
2006-02-17 18:05 ` ron_hylton at hotmail dot com
2006-02-24  0:31 ` mmitchel at gcc dot gnu dot org
2006-05-25  2:41 ` mmitchel at gcc dot gnu dot org
2006-06-15  3:40 ` bangerth at dealii dot org
2006-06-21 20:02 ` ron_hylton at hotmail dot com
2006-07-05 18:03 ` [Bug c++/24605] [4.0/4.1 " jason at gcc dot gnu dot org
2006-10-12  1:06 ` bangerth at dealii dot org
2006-10-12  1:06 ` bangerth at dealii dot org

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=20051105010008.28879.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).