public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/38593] [4.4 regression] ICE: verify_gimple failed Date: Fri, 02 Jan 2009 11:36:00 -0000 [thread overview] Message-ID: <20090102113440.7351.qmail@sourceware.org> (raw) In-Reply-To: <bug-38593-11764@http.gcc.gnu.org/bugzilla/> ------- Comment #6 from jakub at gcc dot gnu dot org 2009-01-02 11:34 ------- That's unexpected. Anyway, if you move away the gch file (or directory), can you still reproduce it and if yes, attach preprocessed source? Otherwise it would be extremely hard to reproduce for anyone... -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38593
next prev parent reply other threads:[~2009-01-02 11:36 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-12-21 12:50 [Bug target/38593] New: " doko at ubuntu dot com 2008-12-21 12:52 ` [Bug target/38593] " doko at ubuntu dot com 2008-12-21 12:52 ` doko at ubuntu dot com 2008-12-21 13:00 ` doko at ubuntu dot com 2008-12-21 17:27 ` [Bug tree-optimization/38593] " pinskia at gcc dot gnu dot org 2008-12-21 17:28 ` pinskia at gcc dot gnu dot org 2008-12-22 10:59 ` doko at ubuntu dot com 2009-01-02 11:36 ` jakub at gcc dot gnu dot org [this message] 2009-01-04 22:08 ` reichelt at gcc dot gnu dot org 2009-01-05 18:37 ` doko at ubuntu dot com 2009-01-05 21:48 ` reichelt at gcc dot gnu dot 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=20090102113440.7351.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).