public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pavel.celba at ricardo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/103096] Compiling never ends (at least not in resonable time - less than 10 mins)
Date: Fri, 05 Nov 2021 11:27:22 +0000	[thread overview]
Message-ID: <bug-103096-4-7MLCnEOpGS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103096-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Pavel Celba <pavel.celba at ricardo dot com> ---
But shouldn't the compiler end in all cases with some error?
There should be a depth instantiation limit which is reached and compilation
ended.
No matter how non-sensible the input is. My input is quite sensible C++ code
bug thing any amateur can easily do.

  parent reply	other threads:[~2021-11-05 11:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-05 10:49 [Bug c++/103096] New: " pavel.celba at ricardo dot com
2021-11-05 11:12 ` [Bug libstdc++/103096] " rguenth at gcc dot gnu.org
2021-11-05 11:27 ` pavel.celba at ricardo dot com [this message]
2021-11-05 11:45 ` [Bug c++/103096] " redi at gcc dot gnu.org
2021-11-05 11:55 ` redi at gcc dot gnu.org
2021-11-05 12:01 ` redi at gcc dot gnu.org
2021-11-05 12:06 ` jakub at gcc dot gnu.org
2021-11-05 12:27 ` redi at gcc dot gnu.org
2021-11-08  8:43 ` pinskia at gcc dot gnu.org
2021-12-08 11:14 ` redi 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-103096-4-7MLCnEOpGS@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).