public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "m.strashun at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/46400] g++ Segmentation Fault on heavily templated project. Date: Tue, 09 Nov 2010 19:36:00 -0000 [thread overview] Message-ID: <bug-46400-4-wPfVtGLS1A@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-46400-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46400 --- Comment #3 from Michael Strashun <m.strashun at gmail dot com> 2010-11-09 19:36:37 UTC --- It seems to me that bug reporting guideline prohibits attaching archives, but, probably, I have misunderstood. I ll try to do my best at reducing, but it is not fast and easy task at all - project compilation time is about 2 mins for me and delta processing takes ages. Original file is quite hard to reduce, too, because nothing will compile at all if I remove any template-realated part - crash happens somewhere at main grammar template resolution time. I ll think what I can do about this.
next prev parent reply other threads:[~2010-11-09 19:36 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-11-09 18:34 [Bug c++/46400] New: " m.strashun at gmail dot com 2010-11-09 18:40 ` [Bug c++/46400] " m.strashun at gmail dot com 2010-11-09 19:00 ` paolo.carlini at oracle dot com 2010-11-09 19:36 ` m.strashun at gmail dot com [this message] 2010-11-09 19:43 ` paolo.carlini at oracle dot com 2010-11-09 19:44 ` paolo.carlini at oracle dot com 2010-11-10 12:08 ` rguenth at gcc dot gnu.org 2010-11-10 12:37 ` m.strashun at gmail dot com 2011-06-23 19:29 ` paolo.carlini at oracle dot com 2011-06-24 10:25 ` jakub at gcc dot gnu.org 2011-06-24 21:11 ` jakub at gcc dot gnu.org 2011-06-24 21:30 ` paolo.carlini at oracle dot com 2011-06-26 16:52 ` jakub at gcc dot gnu.org 2012-04-12 19:17 ` bergner 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-46400-4-wPfVtGLS1A@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).