public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/53752] New: ice in write_array_type
Date: Sat, 23 Jun 2012 08:20:00 -0000	[thread overview]
Message-ID: <bug-53752-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 53752
           Summary: ice in write_array_type
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: dcb314@hotmail.com


I just tried to compile the package device-mapper-persistent-data-0.1.4-1
on gcc-4.8 trunk dated 20120620 on an AMD x86_64 box.

The compiler said

btree.tcc:495:1: internal compiler error: in write_array_type, at
cp/mangle.c:3124
 btree<Levels, ValueTraits>::remove(key const &key)
 ^
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.

Preprocessed source code attached. Flag -g required.


             reply	other threads:[~2012-06-23  8:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-23  8:20 dcb314 at hotmail dot com [this message]
2012-06-23  8:22 ` [Bug c++/53752] " dcb314 at hotmail dot com
2012-06-23 13:45 ` hjl.tools at gmail dot com
2012-06-25  8:02 ` [Bug c++/53752] [4.8 Regression] " rguenth at gcc dot gnu.org
2012-06-25  8:45 ` rguenth at gcc dot gnu.org
2012-06-25  8:50 ` rguenth at gcc dot gnu.org
2012-06-25 17:36 ` jason at gcc dot gnu.org
2012-06-26 13:55 ` rguenth at gcc dot gnu.org
2012-06-26 14:03 ` rguenth at gcc dot gnu.org
2012-06-26 14:03 ` rguenth at gcc dot gnu.org
2012-06-26 14:04 ` rguenth at gcc dot gnu.org
2012-11-27 21:50 ` paolo.carlini at oracle dot com

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-53752-4@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).