public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/99088] Failure to error on recursive template instantiation in a reasonable time
Date: Mon, 15 Feb 2021 17:33:14 +0000 [thread overview]
Message-ID: <bug-99088-4-xC3ppDYJhL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99088-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99088
Patrick Palka <ppalka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ppalka at gcc dot gnu.org
--- Comment #1 from Patrick Palka <ppalka at gcc dot gnu.org> ---
GCC 11 appears to be much slower than GCC 10 here because snapshots of trunk
are by default built with extra checking enabled, and your testcase is
exercising a check in the type comparison code that seems to be quadratic in
the depth of the template instantiation. Release builds (by default) don't
perform this particular check, which is why GCC 10 appears to be much faster.
You can disable most of these sanity checks when using snapshots of trunk by
passing -fno-checking to the compile command line.
next prev parent reply other threads:[~2021-02-15 17:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-13 19:35 [Bug c++/99088] New: " gabravier at gmail dot com
2021-02-15 17:33 ` ppalka at gcc dot gnu.org [this message]
2021-11-08 8:39 ` [Bug c++/99088] " 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-99088-4-xC3ppDYJhL@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).