public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nevin at eviloverlord dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/55826] New: -ftime-report causes internal compiler error with Boost.Asio
Date: Fri, 28 Dec 2012 19:53:00 -0000	[thread overview]
Message-ID: <bug-55826-4@http.gcc.gnu.org/bugzilla/> (raw)


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

             Bug #: 55826
           Summary: -ftime-report causes internal compiler error with
                    Boost.Asio
    Classification: Unclassified
           Product: gcc
           Version: 4.7.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: nevin@eviloverlord.com


Created attachment 29059
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29059
Original source file

Compiling the following test program (using Boost 1.52):

#include <boost/asio/ip/tcp.hpp>

void CrashTimeReport()
{

    boost::asio::ip::tcp::resolver::iterator it;
    *it;    // crashes
}


with

g++-4.7 -v -ftime-report -std=c++0x -save-temps Dns.cpp


/site/apps/gcc-4.7.2-drw.patched.6/lib/gcc/x86_64-linux-gnu/4.7.2/../../../../include/c++/4.7.2/bits/alloc_traits.h:48:11:
internal compiler error: in timevar_start, at timevar.c:344


The full output and preprocessed source file is attached.


             reply	other threads:[~2012-12-28 19:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-28 19:53 nevin at eviloverlord dot com [this message]
2012-12-28 19:56 ` [Bug c++/55826] " nevin at eviloverlord dot com
2012-12-28 19:56 ` nevin at eviloverlord dot com
2012-12-31 10:43 ` pinskia at gcc dot gnu.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-55826-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).