public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ktietz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/64100] A static assert using the the current class in a noexcept test leads to a segfault
Date: Thu, 04 Dec 2014 11:22:00 -0000 [thread overview]
Message-ID: <bug-64100-4-UiYQ6nANgV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64100-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64100
Kai Tietz <ktietz at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--- Comment #5 from Kai Tietz <ktietz at gcc dot gnu.org> ---
(In reply to Jason Merrill from comment #4)
> (In reply to Kai Tietz from comment #2)
> > Following patch fixes this issue for me:
>
> Were you going to send the patch to the list?
Yes, I will send it today to ML. I will put you CC.
> > + if (!expr)
> > + {
> > + cxx_incomplete_type_error (dtor_name, dtor_type);
> > + return error_mark_node;
> > + }
>
> The error needs to be conditional on (complain & tf_error).
Ok, I'll add that.
> Does the caller handle error_mark_node properly?
Yes, I tested it before. By just returning error_mark_node the testcase will
be processed completely silently by g++.
next prev parent reply other threads:[~2014-12-04 11:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-28 10:57 [Bug c++/64100] New: " ville.voutilainen at gmail dot com
2014-12-03 9:49 ` [Bug c++/64100] " mpolacek at gcc dot gnu.org
2014-12-03 10:38 ` ktietz at gcc dot gnu.org
2014-12-03 15:52 ` jakub at gcc dot gnu.org
2014-12-03 21:56 ` jason at gcc dot gnu.org
2014-12-04 11:22 ` ktietz at gcc dot gnu.org [this message]
2014-12-10 11:23 ` ktietz at gcc dot gnu.org
2014-12-10 11:27 ` ktietz at gcc dot gnu.org
2014-12-10 16:28 ` ktietz 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-64100-4-UiYQ6nANgV@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).