public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mizvekov at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/59761] ICE: g++ segfaults in test case involving constexpr default constructor with uninitialized member and template type alias Date: Fri, 10 Jan 2014 17:42:00 -0000 [thread overview] Message-ID: <bug-59761-4-dwFkemf1fz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59761-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59761 --- Comment #2 from Matheus Izvekov <mizvekov at gmail dot com> --- Created attachment 31805 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=31805&action=edit gcc accepts this This one is the same as test_bad.cc, except that the bar member of foo gets initialized by the default constructor.
next prev parent reply other threads:[~2014-01-10 17:42 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-01-10 17:37 [Bug c++/59761] New: " mizvekov at gmail dot com 2014-01-10 17:42 ` mizvekov at gmail dot com [this message] 2015-03-16 15:08 ` [Bug c++/59761] " mpolacek at gcc dot gnu.org 2015-06-23 8:47 ` rguenth 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-59761-4-dwFkemf1fz@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: linkBe 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).