public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/56095] [4.6/4.7/4.8 Regression] Crash casting function pointer as non-type template argument Date: Thu, 24 Jan 2013 12:11:00 -0000 [thread overview] Message-ID: <bug-56095-4-J5EpVYTYfc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56095-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56095 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org Summary|Crash casting function |[4.6/4.7/4.8 Regression] |pointer as non-type |Crash casting function |template argument |pointer as non-type | |template argument --- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> 2013-01-24 12:11:13 UTC --- I can, with everything starting from http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=166167 You need --enable-checking=yes compiler though.
next prev parent reply other threads:[~2013-01-24 12:11 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-01-24 5:23 [Bug c++/56095] New: " spoo at zarbosoft dot com 2013-01-24 6:39 ` [Bug c++/56095] " spoo at zarbosoft dot com 2013-01-24 11:56 ` daniel.kruegler at googlemail dot com 2013-01-24 12:02 ` redi at gcc dot gnu.org 2013-01-24 12:08 ` daniel.kruegler at googlemail dot com 2013-01-24 12:11 ` jakub at gcc dot gnu.org [this message] 2013-01-24 12:12 ` [Bug c++/56095] [4.6/4.7/4.8 Regression] " jakub at gcc dot gnu.org 2013-01-24 12:14 ` redi at gcc dot gnu.org 2013-01-25 20:01 ` jason at gcc dot gnu.org 2013-01-25 20:05 ` [Bug c++/56095] [4.6/4.7 " jakub at gcc dot gnu.org 2013-01-25 20:20 ` jason at gcc dot gnu.org 2013-03-17 2:34 ` 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-56095-4-J5EpVYTYfc@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).