public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jvp4846 at g dot rit.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/65198] New: [4.9 regression] User-defined literal template inside generic lambda segfaults GCC 5.0
Date: Tue, 24 Feb 2015 23:42:00 -0000	[thread overview]
Message-ID: <bug-65198-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 65198
           Summary: [4.9 regression] User-defined literal template inside
                    generic lambda segfaults GCC 5.0
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: jvp4846 at g dot rit.edu

Created attachment 34862
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34862&action=edit
Sample code

The attached code causes a segfault under GCC 5.0*, but compiles successfully
under GCC 4.9.2.

* From the Debian repo. Apologies in advance if this is already fixed or is
just a bug in Debian's binary; I won't have time to self-build GCC anytime
soon. The version is as follows:

g++ (Debian 20150211-1) 5.0.0 20150211 (experimental) [trunk revision 220605]


             reply	other threads:[~2015-02-24 22:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-24 23:42 jvp4846 at g dot rit.edu [this message]
2015-02-25 12:13 ` [Bug c++/65198] " rguenth at gcc dot gnu.org
2015-02-25 12:19 ` [Bug c++/65198] [5 Regression] " rguenth at gcc dot gnu.org
2015-02-25 16:44 ` mpolacek at gcc dot gnu.org
2015-02-25 18:22 ` [Bug c++/65198] [4.9 Regression] User-defined literal template inside generic lambda segfaults jakub at gcc dot gnu.org
2015-06-26 20:19 ` jakub at gcc dot gnu.org
2015-06-26 20:39 ` jakub 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-65198-4@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).