public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bangerth at dealii dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/33590] c++ crash in KDE's qca module Date: Mon, 01 Oct 2007 01:10:00 -0000 [thread overview] Message-ID: <20071001011048.19035.qmail@sourceware.org> (raw) In-Reply-To: <bug-33590-15166@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from bangerth at dealii dot org 2007-10-01 01:10 ------- On big files, this is what can happen with optimized builds... -- bangerth at dealii dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33590
prev parent reply other threads:[~2007-10-01 1:10 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-09-29 18:09 [Bug c++/33590] New: " dancecile at gmail dot com 2007-09-29 18:35 ` [Bug c++/33590] " dancecile at gmail dot com 2007-09-29 19:01 ` rguenth at gcc dot gnu dot org 2007-09-29 19:33 ` dancecile at gmail dot com 2007-10-01 1:10 ` bangerth at dealii dot org [this message]
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=20071001011048.19035.qmail@sourceware.org \ --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).