public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: carlo@alinoe.com
To: gcc-gnats@gcc.gnu.org
Subject: c++/10486: Regression (ICE) in 3.3 branch due to recent patch.
Date: Fri, 25 Apr 2003 00:06:00 -0000	[thread overview]
Message-ID: <20030425000533.1262.qmail@sources.redhat.com> (raw)


>Number:         10486
>Category:       c++
>Synopsis:       Regression (ICE) in 3.3 branch due to recent patch.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          ice-on-legal-code
>Submitter-Id:   net
>Arrival-Date:   Fri Apr 25 00:06:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Carlo Wood
>Release:        GNU C++ version 3.3 20030424 (prerelease)
>Organization:
>Environment:
i686-pc-linux-gnu
>Description:
After updating my CVS source tree at 20030424,
while the last update was from around 20030404,
I ran into a new ICE.

This is a regression, all previous versions compile
this fine, as did version 3.3 20030404.

Full output:

g++-cvs-3.3 -v -c troep.cc
Reading specs from /usr/local/gcc-cvs-3.3/lib/gcc-lib/i686-pc-linux-gnu/3.3/specs
Configured with: /usr/src/gcc/gcc-cvs-3.3/configure --prefix=/usr/local/gcc-cvs-3.3 --enable-shared --with-gnu-as --with-gnu-ld --enable-languages=c++ --enable-debug --enable-threads
Thread model: posix
gcc version 3.3 20030424 (prerelease)
 /usr/local/gcc-cvs-3.3/lib/gcc-lib/i686-pc-linux-gnu/3.3/cc1plus -quiet -v -D__GNUC__=3 -D__GNUC_MINOR__=3 -D__GNUC_PATCHLEVEL__=0 -D_GNU_SOURCE troep.cc -D__GNUG__=3 -quiet -dumpbase troep.cc -auxbase troep -version -o /tmp/ccpOnYTr.s
GNU C++ version 3.3 20030424 (prerelease) (i686-pc-linux-gnu)
        compiled by GNU C version 3.3 20030424 (prerelease).
GGC heuristics: --param ggc-min-expand=55 --param ggc-min-heapsize=48296
ignoring nonexistent directory "/usr/local/gcc-cvs-3.3/i686-pc-linux-gnu/include"
#include "..." search starts here:
#include <...> search starts here:
 /usr/local/gcc-cvs-3.3/include/c++/3.3
 /usr/local/gcc-cvs-3.3/include/c++/3.3/i686-pc-linux-gnu
 /usr/local/gcc-cvs-3.3/include/c++/3.3/backward
 /usr/local/include
 /usr/local/gcc-cvs-3.3/include
 /usr/local/gcc-cvs-3.3/lib/gcc-lib/i686-pc-linux-gnu/3.3/include
 /usr/include
End of search list.
troep.cc: In constructor `A<_Tp, _Alloc>::A(typename
   _Alloc::rebind<_Tp>::other&) [with _Tp = int, _Alloc = B<int>]':
troep.cc:19: 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.
>How-To-Repeat:
Compile the following code snippet:


template<typename _Tp, typename _Alloc>
  struct A
  {
    typedef typename _Alloc::template rebind<_Tp>::other allocator_type;
    A(allocator_type const& __a = allocator_type()) { }
  };

template<typename T>
  struct B
  {
    template <typename T1>
      struct rebind
      {
        typedef B<T1> other;
      };
    ~B() { }
  };

A<int, B<char>::rebind<int>::other> x;
>Fix:
Among others, removing the "~B() { }" helps.
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2003-04-25  0:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-25  0:06 carlo [this message]
2003-04-25  0:20 bangerth
2003-04-25  0:46 Carlo Wood
2003-04-25  0:56 Wolfgang Bangerth
2003-04-25  1:56 Carlo Wood
2003-04-25 15:08 bangerth

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=20030425000533.1262.qmail@sources.redhat.com \
    --to=carlo@alinoe.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).