public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "reichelt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/59066] [C++11] 'using' instead of 'typedef' causes a segmentation fault.
Date: Wed, 26 Feb 2014 21:56:00 -0000	[thread overview]
Message-ID: <bug-59066-4-zwRy3MnmMQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59066-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59066

Volker Reichelt <reichelt at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jason at gcc dot gnu.org

--- Comment #5 from Volker Reichelt <reichelt at gcc dot gnu.org> ---
Jason, your patch for PR60182 seems to have fixed this one, too.
Do you want to add the reduced testcase (in comment#4) to the testsuite?


  parent reply	other threads:[~2014-02-26 21:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-10 11:44 [Bug c++/59066] New: Segmentation fault alexandre.hamez at gmail dot com
2013-11-10 12:03 ` [Bug c++/59066] " alexandre.hamez at gmail dot com
2013-11-10 13:00 ` redi at gcc dot gnu.org
2013-11-10 13:22 ` [Bug c++/59066] C+11, 'using' instead of 'typedef' causes a segmentation fault alexandre.hamez at gmail dot com
2013-11-13  9:34 ` [Bug c++/59066] C++11, " paolo.carlini at oracle dot com
2014-02-14 21:16 ` [Bug c++/59066] [C++11] " reichelt at gcc dot gnu.org
2014-02-26 21:56 ` reichelt at gcc dot gnu.org [this message]
2014-02-27 17:04 ` jason 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-59066-4-zwRy3MnmMQ@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).