public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/43113] too long diagnostics in some cases of recursive template instantiation
Date: Tue, 20 May 2014 16:06:00 -0000 [thread overview]
Message-ID: <bug-43113-4-C0qVhVk9Zt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-43113-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43113
Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |paolo.carlini at oracle dot com
Depends on| |16564
--- Comment #5 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
I don't want to mark it as a duplicate because PR16564 is a bit more complex.
I think this one should be easier to fix. We could always print:
pr43113.C:7:11: error: template instantiation depth exceeds maximum of 10 (use
-ftemplate-depth= to increase the maximum) instantiating ‘struct
A<[...]<A<B>::S>[...]>::S>’
pr43113.C:7:11: recursively instantiated from ‘A<A<B>::S>’
pr43113.C:7:11: instantiated from ‘A<B>’
pr43113.C:10:20: instantiated from here
pr43113.C:7:11: error: ‘A<S>::ht’ has incomplete type
>From gcc-bugs-return-452055-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue May 20 16:36:20 2014
Return-Path: <gcc-bugs-return-452055-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18941 invoked by alias); 20 May 2014 16:36:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 18560 invoked by uid 48); 20 May 2014 16:36:14 -0000
From: "doko at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/61231] [4.9/4.10 Regression] bootstrap comparision failure on powerpc64le-linux-gnu
Date: Tue, 20 May 2014 16:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: doko at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.9.1
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-61231-4-dH3aIGVMZ5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61231-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61231-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-05/txt/msg01747.txt.bz2
Content-length: 218
https://gcc.gnu.org/bugzilla/show_bug.cgi?ida231
--- Comment #8 from Matthias Klose <doko at gcc dot gnu.org> ---
on powerpc64le, the test passes with both the stage2 and stage3 compilers of
the problematic build.
next parent reply other threads:[~2014-05-20 16:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-43113-4@http.gcc.gnu.org/bugzilla/>
2014-05-20 16:06 ` manu at gcc dot gnu.org [this message]
2014-09-30 17:36 ` paolo.carlini at oracle dot com
2021-12-16 23:09 ` pinskia at gcc dot gnu.org
2010-02-18 13:30 [Bug c++/43113] New: " zsojka at seznam dot cz
2010-02-18 14:19 ` [Bug c++/43113] " paolo dot carlini at oracle dot com
2010-02-20 0:36 ` manu at gcc dot gnu dot org
2010-02-20 0:36 ` manu at gcc dot gnu dot org
2010-04-28 8:46 ` manu 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-43113-4-C0qVhVk9Zt@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).