public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marcus at jet dot franken dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/35894] New: ICE in calc_dfs_tree, at dominance.c:393 Date: Wed, 09 Apr 2008 21:54:00 -0000 [thread overview] Message-ID: <bug-35894-3760@http.gcc.gnu.org/bugzilla/> (raw) /home/marcus/projects/gcc.trunk/BIN/bin/gcc -m32 -c -O3 ati_fragment_shader.i ati_fragment_shader.i: In function 'g': ati_fragment_shader.i:39: internal compiler error: in calc_dfs_tree, at dominance.c:393 -- Summary: ICE in calc_dfs_tree, at dominance.c:393 Product: gcc Version: 4.4.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: marcus at jet dot franken dot de GCC build triplet: i686-pc-linux-gnu GCC host triplet: x86_64-unknown-linux-gnu GCC target triplet: x86_64-unknown-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35894
next reply other threads:[~2008-04-09 21:54 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-04-09 21:54 marcus at jet dot franken dot de [this message] 2008-04-09 21:54 ` [Bug c/35894] " marcus at jet dot franken dot de 2008-04-10 10:32 ` [Bug tree-optimization/35894] " rguenth 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=bug-35894-3760@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).