public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steven at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/16564] g++ seems to go into an infinite loop after errors
Date: Thu, 08 Nov 2012 23:18:00 -0000 [thread overview]
Message-ID: <bug-16564-4-00DUh3eQhc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-16564-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16564
Steven Bosscher <steven at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic
Last reconfirmed|2008-12-25 15:59:38 |2012-11-08 15:59:38
--- Comment #11 from Steven Bosscher <steven at gcc dot gnu.org> 2012-11-08 23:17:40 UTC ---
The compiler now produces a wonderful diagnostic for my original test case
(comment #1), with one line of the diagnostic with a length of 30750 (!)
characters. Nice, on that 80-chars wide terminal! :-)
t.C: In instantiation of 'class
std::vector<std::allocator<std::allocator<std::allocator<std::allocator<std::allocator<std::allocator<std::allocator<std::allocator<std::allocat.....
t.C:120:23: recursively required from 'class
std::vector<std::allocator<__gnu_cxx::_Hashtable_node<std::pair<const
std::basic_string<char>, symbol> >*>, std::allocator<std::a.....
t.C:120:23: required from 'class
std::vector<__gnu_cxx::_Hashtable_node<std::pair<const std::basic_string<char>,
symbol> >*, std::allocator<__gnu_cxx::_Hashtable_node<std::pa......
t.C:445:18: required from 'class __gnu_cxx::hashtable<std::pair<const
std::basic_string<char>, symbol>, std::basic_string<char>,
__gnu_cxx::hash<std::basic_string<char> >, st.....
t.C:552:9: required from 'class __gnu_cxx::hash_map<std::basic_string<char>,
symbol>'
t.C:574:35: required from here
t.C:121:38: error: no type named 'pointer' in 'class
std::allocator<std::allocator<std::allocator<std::allocator<std::allocator<std::allocator<std::allocator<std::allocator<std....
typedef typename _Alloc::pointer pointer;
^
next parent reply other threads:[~2012-11-08 23:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-16564-4@http.gcc.gnu.org/bugzilla/>
2012-11-08 23:18 ` steven at gcc dot gnu.org [this message]
2012-11-09 0:44 ` manu at gcc dot gnu.org
2012-11-09 0:58 ` manu at gcc dot gnu.org
2012-11-09 1:28 ` manu at gcc dot gnu.org
2013-04-09 17:38 ` paolo.carlini at oracle dot com
2013-04-09 18:04 ` manu at gcc dot gnu.org
2013-04-09 18:11 ` paolo.carlini at oracle dot com
2013-12-27 17:06 ` reichelt at gcc dot gnu.org
2013-12-27 20:37 ` manu at gcc dot gnu.org
2013-12-29 19:15 ` manu at gcc dot gnu.org
2014-09-30 9:35 ` paolo.carlini at oracle dot com
2014-09-30 14:28 ` manu at gcc dot gnu.org
2014-09-30 17:29 ` manu at gcc dot gnu.org
2014-09-30 17:36 ` paolo.carlini at oracle dot com
[not found] <bug-16564-280@http.gcc.gnu.org/bugzilla/>
2008-12-25 16:03 ` tkoenig at gcc dot gnu dot org
2004-07-15 11:05 [Bug c++/16564] New: g++ goes " steven at gcc dot gnu dot org
2004-10-18 12:15 ` [Bug c++/16564] g++ seems to go " reichelt at gcc dot gnu dot org
2004-10-18 15:47 ` bangerth at dealii dot org
2004-10-18 16:05 ` reichelt at gcc dot gnu dot org
2004-10-18 17:14 ` bangerth at dealii dot org
2005-01-17 0:42 ` pinskia at gcc dot gnu dot 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-16564-4-00DUh3eQhc@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).