public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/63936] [5.0 regression] ICE: libstdc++-v3/include/chrono:725:66: internal compiler error: in adjust_temp_type, at cp/constexpr.c:1020
Date: Tue, 18 Nov 2014 16:00:00 -0000	[thread overview]
Message-ID: <bug-63936-4-WTqpLEC8du@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63936-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63936

--- Comment #2 from ktkachov at gcc dot gnu.org ---
Created attachment 34026
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34026&action=edit
tarball of preprocessed file that ICEs

I'm attaching the preprocessed file that ICEs.
It just needs a -std=gnu++0x when compiling with an arm cross compiler, any
optimisation level (the ICE is in the parser)


  parent reply	other threads:[~2014-11-18 16:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-18 15:21 [Bug c++/63936] New: " ktkachov at gcc dot gnu.org
2014-11-18 15:30 ` [Bug c++/63936] [5.0 regression] " ramana at gcc dot gnu.org
2014-11-18 15:34 ` ktkachov at gcc dot gnu.org
2014-11-18 16:00 ` ktkachov at gcc dot gnu.org [this message]
2014-11-18 17:13 ` ktkachov 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-63936-4-WTqpLEC8du@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).