[Bug tree-optimization/22135] The gcc-4.1-20050611 compiler ICE's using -ftree-vectorize in conjunction with -fdump-tree-all-details-stats

2005-07-14 Thread Ralf_Recker at gmx dot de
--- Additional Comments From Ralf_Recker at gmx dot de 2005-07-14 07:21 --- (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

[Bug tree-optimization/22135] The gcc-4.1-20050611 compiler ICE's using -ftree-vectorize in conjunction with -fdump-tree-all-details-stats

2005-07-11 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-07-12 00:12 --- (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

[Bug tree-optimization/22135] The gcc-4.1-20050611 compiler ICE's using -ftree-vectorize in conjunction with -fdump-tree-all-details-stats

2005-07-05 Thread Ralf_Recker at gmx dot de
--- Additional Comments From Ralf_Recker at gmx dot de 2005-07-05 07:25 --- (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

[Bug tree-optimization/22135] The gcc-4.1-20050611 compiler ICE's using -ftree-vectorize in conjunction with -fdump-tree-all-details-stats

2005-07-05 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-07-05 12:56 --- (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

[Bug tree-optimization/22135] The gcc-4.1-20050611 compiler ICE's using -ftree-vectorize in conjunction with -fdump-tree-all-details-stats

2005-07-03 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-07-03 11:52 --- (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 tree-optimization/22135] The gcc-4.1-20050611 compiler ICE's using -ftree-vectorize in conjunction with -fdump-tree-all-details-stats

2005-06-23 Thread Ralf_Recker at gmx dot de
--- Additional Comments From Ralf_Recker at gmx dot de 2005-06-23 07:08 --- gcc-4.1-20050618 ICE's with the same error message. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22135

[Bug tree-optimization/22135] The gcc-4.1-20050611 compiler ICE's using -ftree-vectorize in conjunction with -fdump-tree-all-details-stats

2005-06-23 Thread Ralf_Recker at gmx dot de
--- Additional Comments From Ralf_Recker at gmx dot de 2005-06-23 08:40 --- P.S.: Why comes .c.t59.copyprop4 before .c.t72.copyprop3 (At that point the ICE seems to occur)? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22135

[Bug tree-optimization/22135] The gcc-4.1-20050611 compiler ICE's using -ftree-vectorize in conjunction with -fdump-tree-all-details-stats

2005-06-21 Thread Ralf_Recker at gmx dot de
--- Additional Comments From Ralf_Recker at gmx dot de 2005-06-21 07:25 --- To all attendants of the developer summit: Greet the elks (moose?) from me ;-) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22135

[Bug tree-optimization/22135] The gcc-4.1-20050611 compiler ICE's using -ftree-vectorize in conjunction with -fdump-tree-all-details-stats

2005-06-21 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-06-21 12:48 --- 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 *** -- What|Removed