public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/96137] [11 Regression] GCC hang on in invalid function definition
Date: Thu, 09 Jul 2020 18:03:26 +0000 [thread overview]
Message-ID: <bug-96137-4-iqmJq6COXu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96137-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96137
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2020-07-09
Status|UNCONFIRMED |ASSIGNED
Target Milestone|--- |11.0
Keywords| |compile-time-hog
CC| |mpolacek at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |mpolacek at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #2 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Started with my:
r11-86-gef3479afc5ab415f00a53fc6f6a990df7f6a0747
(In reply to Haoxin Tu from comment #1)
> Also, I want to know are those cases (invalid code but makes GCC hang on)
> worth reporting? If those cases can help improve the GCC FE or its
> performance, I will continue to file more reports. Otherwise, I will just
> stop doing that.
I would treat them just like ICEs. They are useful if the testcase isn't
complete garbage. This one is sort of useful because it shows that my change
above has a corner case that I didn't consider.
next prev parent reply other threads:[~2020-07-09 18:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 15:25 [Bug c++/96137] New: " haoxintu at gmail dot com
2020-07-09 16:01 ` [Bug c++/96137] " haoxintu at gmail dot com
2020-07-09 18:03 ` mpolacek at gcc dot gnu.org [this message]
2020-07-09 18:09 ` haoxintu at gmail dot com
2020-07-28 9:15 ` haoxintu at gmail dot com
2020-10-12 12:48 ` rguenth at gcc dot gnu.org
2021-01-28 22:32 ` mpolacek at gcc dot gnu.org
2021-01-29 4:30 ` cvs-commit at gcc dot gnu.org
2021-01-29 4:32 ` mpolacek 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-96137-4-iqmJq6COXu@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).