public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dje at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/18168] New: SPEC CPU2000 173.applu tree-loop-linear failure Date: Wed, 27 Oct 2004 00:55:00 -0000 [thread overview] Message-ID: <20041027005509.18168.dje@gcc.gnu.org> (raw) gcc -O3 -ftree-loop-linear applu.f produces error: Dependence relation cannot be represented by distance vector. -- Summary: SPEC CPU2000 173.applu tree-loop-linear failure Product: gcc Version: 4.0.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: tree-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: dje at gcc dot gnu dot org CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: *-*-* GCC host triplet: *-*-* GCC target triplet: *-*-* http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18168
next reply other threads:[~2004-10-27 0:55 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-10-27 0:55 dje at gcc dot gnu dot org [this message] 2004-10-27 0:55 ` [Bug tree-optimization/18168] SPEC CPU2000 173.applu tree-loop-linear ICE dje at gcc dot gnu dot org 2004-10-28 15:31 ` dje at gcc dot gnu dot org 2004-10-28 15:52 ` pinskia at gcc dot gnu dot org 2004-10-28 16:31 ` dberlin at dberlin dot org 2004-10-28 16:36 ` dberlin at dberlin dot org 2004-10-28 16:51 ` reichelt at gcc dot gnu dot org 2004-10-28 16:55 ` dberlin at dberlin dot org 2004-10-30 2:03 ` dberlin at gcc dot gnu dot org 2004-10-30 3:10 ` dberlin at gcc dot gnu dot org 2004-10-30 13:06 ` giovannibajo at libero dot it 2004-10-30 13:15 ` dberlin at dberlin dot org 2004-11-01 18:08 ` cvs-commit at gcc dot gnu dot org 2004-11-01 19:22 ` dberlin at gcc dot gnu dot org 2004-11-06 15:50 ` pinskia 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=20041027005509.18168.dje@gcc.gnu.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).