Summary: | The gcc-4.1-20050611 compiler ICE's using -ftree-vectorize in conjunction with -fdump-tree-all-details-stats | ||
---|---|---|---|
Product: | gcc | Reporter: | Ralf Recker <Ralf_Recker> |
Component: | tree-optimization | Assignee: | Not yet assigned to anyone <unassigned> |
Status: | RESOLVED DUPLICATE | ||
Severity: | minor | CC: | gcc-bugs |
Priority: | P2 | ||
Version: | 4.1.0 | ||
Target Milestone: | --- | ||
Host: | i586-pc-linux-gnu | Target: | i586-pc-linux-gnu |
Build: | i586-pc-linux-gnu | Known to work: | |
Known to fail: | Last reconfirmed: |
Description
Ralf Recker
2005-06-21 07:13:54 UTC
To all attendants of the developer summit: Greet the elks (moose?) from me ;-) This is a dup of bug 22029 which I reported. Thanks for your bug report, hopefully someone will fix this soon. *** This bug has been marked as a duplicate of 22029 *** gcc-4.1-20050618 ICE's with the same error message. P.S.: Why comes .c.t59.copyprop4 before .c.t72.copyprop3 (At that point the ICE seems to occur)? (In reply to comment #4) > P.S.: Why comes .c.t59.copyprop4 before .c.t72.copyprop3 (At that point the ICE > seems to occur)? I forgot to mention this is due to how tree-optimizate works, it is really a bug (a known one), please file so we don't lose track of it. (In reply to comment #5) > I forgot to mention this is due to how tree-optimizate works, it is really a bug (a known one), please file > so we don't lose track of it. Sorry, I didn't understood your answer fully (stupid me :-) So is it entered in the BugZilla database, shall I enter it or shall we leave it alone? Ralf Recker (In reply to comment #6) > Sorry, I didn't understood your answer fully (stupid me :-) > So is it entered in the BugZilla database, shall I enter it or shall we leave it > alone? It is known meaning people have reported it to the GCC list before but that is it. A new bugzilla bug would be nice to keep track of it. (In reply to comment #7) > It is known meaning people have reported it to the GCC list before but that is it. > A new bugzilla bug would be nice to keep track of it. I just found there was a bug was already filed: PR 20962. (In reply to comment #8) > (In reply to comment #7) > > It is known meaning people have reported it to the GCC list before but that is it. > > A new bugzilla bug would be nice to keep track of it. > > I just found there was a bug was already filed: PR 20962. > Thank you very much! |