public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "reichelt at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/39060] [4.4 regression] ICE with lots of invalid member functions Date: Mon, 09 Feb 2009 22:58:00 -0000 [thread overview] Message-ID: <20090209225822.5276.qmail@sourceware.org> (raw) In-Reply-To: <bug-39060-1771@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from reichelt at gcc dot gnu dot org 2009-02-09 22:58 ------- I can still reproduce it with trunk from 2009-02-07 (updated after your comment). As mentioned before the testcase is a little fragile. Some weeks ago I had a much larger testcase (about 150 lines) which I couldn't reduce any further. To me this looks like some fishy memory access. -- reichelt at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- GCC host triplet| |i686-pc-linux-gnu GCC target triplet| |i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39060
next prev parent reply other threads:[~2009-02-09 22:58 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-02-01 11:24 [Bug c++/39060] New: " reichelt at gcc dot gnu dot org 2009-02-01 11:24 ` [Bug c++/39060] " reichelt at gcc dot gnu dot org 2009-02-01 13:17 ` rguenth at gcc dot gnu dot org 2009-02-07 11:36 ` paolo dot carlini at oracle dot com 2009-02-09 22:58 ` reichelt at gcc dot gnu dot org [this message] 2009-02-10 0:09 ` paolo dot carlini at oracle dot com 2009-02-12 23:22 ` bangerth at gmail dot com 2009-02-14 23:38 ` hjl dot tools at gmail dot com 2009-02-23 2:36 ` hjl dot tools at gmail dot com 2009-03-07 19:44 ` hjl dot tools at gmail dot com 2009-03-08 17:29 ` hjl at gcc dot gnu dot org 2009-03-08 17:34 ` hjl dot tools at gmail dot com [not found] <bug-39060-4@http.gcc.gnu.org/bugzilla/> 2022-10-31 22:05 ` pinskia 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=20090209225822.5276.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).