public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "yan12125 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/65882] New: Internal compiler error: Error reporting routines re-entered
Date: Sat, 25 Apr 2015 08:29:00 -0000 [thread overview]
Message-ID: <bug-65882-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65882
Bug ID: 65882
Summary: Internal compiler error: Error reporting routines
re-entered
Product: gcc
Version: 5.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: yan12125 at gmail dot com
I invoke the following command:
g++ -nostdlib -Wbool-compare -Wno-unused -Wno-deprecated-declarations -s
-std=c++11 json.ii
json.ii is the attached file. It's from hhvm.
https://github.com/facebook/folly/blob/master/folly/json.cpp
I encounter no problem if compiling folly separately. If I compile the whole
hhvm, the following error occurs.
The result is:
https://gist.github.com/yan12125/b5498cb6ac2be4a5649a
The compiler version is:
$ g++ -v
Using built-in specs.
COLLECT_GCC=g++
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-unknown-linux-gnu/5.1.0/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with: /build/gcc-multilib/src/gcc-5.1.0/configure --prefix=/usr
--libdir=/usr/lib --libexecdir=/usr/lib --mandir=/usr/share/man
--infodir=/usr/share/info --with-bugurl=https://bugs.archlinux.org/
--enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++ --enable-shared
--enable-threads=posix --with-system-zlib --with-isl --enable-__cxa_atexit
--disable-libunwind-exceptions --enable-clocale=gnu --disable-libstdcxx-pch
--disable-libssp --enable-gnu-unique-object --enable-linker-build-id
--enable-lto --enable-plugin --enable-install-libiberty
--with-linker-hash-style=gnu --enable-gnu-indirect-function --enable-multilib
--disable-werror --enable-checking=release --with-default-libstdcxx-abi=c++98
Thread model: posix
gcc version 5.1.0 (GCC)
OS: Arch Linux x86_64
I use the official gcc-multilib package
$ pacman -Qi gcc-multilib
Name : gcc-multilib
Version : 5.1.0-1
Description : The GNU Compiler Collection - C and C++ frontends for multilib
Architecture : x86_64
URL : http://gcc.gnu.org
Licenses : GPL LGPL FDL custom
Groups : multilib-devel
Provides : gcc=5.1.0-1
Depends On : gcc-libs-multilib=5.1.0-1 binutils>=2.25 libmpc
Optional Deps : None
Required By : clang dkms dmd
Optional For : None
Conflicts With : gcc
Replaces : None
Installed Size : 108.38 MiB
Packager : Jan Alexander Steffens (heftig) <jan.steffens@gmail.com>
Build Date : Thu 23 Apr 2015 09:33:01 PM CST
Install Date : Sat 25 Apr 2015 01:48:42 PM CST
Install Reason : Explicitly installed
Install Script : Yes
Validated By : Signature
next reply other threads:[~2015-04-25 8:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-25 8:29 yan12125 at gmail dot com [this message]
2015-04-25 8:49 ` [Bug c++/65882] " trippels at gcc dot gnu.org
2015-04-25 9:14 ` yan12125 at gmail dot com
2015-04-25 9:39 ` [Bug c++/65882] [5/6 Regression] " trippels at gcc dot gnu.org
2015-04-27 9:05 ` rguenth at gcc dot gnu.org
2015-04-28 6:45 ` maltsevm at gmail dot com
2015-06-09 8:01 ` trippels at gcc dot gnu.org
2015-06-24 0:53 ` miyuki at gcc dot gnu.org
2015-06-24 0:57 ` miyuki 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-65882-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).