public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tbm at cyrius dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/29105]  New: [4.2 Regression] segfault in add_candidates
Date: Sat, 16 Sep 2006 11:55:00 -0000	[thread overview]
Message-ID: <bug-29105-12387@http.gcc.gnu.org/bugzilla/> (raw)

I get the following segfault with current mainline that I didn't get with
20060823:

(sid)312:tbm@em64t: ~] /usr/lib/gcc-snapshot/bin/g++ -c adept-tagfilter.cc
adept-tagfilter.cc: In constructor 'aptFront::TagFilter<T>::TagFilter()':
adept-tagfilter.cc:45: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
(sid)313:tbm@em64t: ~] g++ -c adept-tagfilter.cc
(sid)314:tbm@em64t: ~]

Testcase:

namespace aptFront
{
  namespace cache
  {
    namespace component
    {
      class Tags;
    }
    class Observer
    {
      template < typename T > void observeComponent ();
    };
  }
  namespace utils
  {
    template < typename T > struct MultiTypeBase
    {
    };
    const int notComparable = 0;
    const int equalityComparable = 1;
      template < typename Self, typename Base, int comparable =
      notComparable > struct MultiTypeImpl:public Base {
    };
  }
  namespace predicate
  {
    template < typename T > struct Base:public utils::MultiTypeBase < Base <
      T > >
    {
    };
      template < typename T, typename Self, typename Base =
      Base < T > >struct Implementation:utils::MultiTypeImpl < Self, Base,
      utils::equalityComparable >
    {
    };
  }
  struct InterfacingPredicate
  {
  };
    template < typename T > struct TagFilter:predicate::Implementation < T,
    TagFilter < T > >, InterfacingPredicate, cache::Observer
  {
    TagFilter ()
    {
      observeComponent < cache::component::Tags > ();
    }
  };
}


-- 
           Summary: [4.2 Regression] segfault in add_candidates
           Product: gcc
           Version: 4.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: tbm at cyrius dot com


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


             reply	other threads:[~2006-09-16 11:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-16 11:55 tbm at cyrius dot com [this message]
2006-09-16 11:56 ` [Bug c++/29105] " tbm at cyrius dot com
2006-09-16 16:00 ` pinskia at gcc dot gnu dot org
2006-09-17  9:08 ` pinskia at gcc dot gnu dot org
2006-09-18 19:23 ` [Bug c++/29105] [4.2 Regression] segfault in add_candidates with a non template base class and a template member function janis at gcc dot gnu dot org
2006-09-20 22:50 ` mmitchel at gcc dot gnu dot org
2006-10-02  1:28 ` mmitchel at gcc dot gnu dot org
2006-10-02  4:13 ` mmitchel at gcc dot gnu dot org
2006-10-02  4:34 ` mmitchel at gcc dot gnu dot org
2006-10-05 20:31 ` reichelt at gcc dot gnu 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=bug-29105-12387@http.gcc.gnu.org/bugzilla/ \
    --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).