--- Additional Comments From pinskia at gcc dot gnu dot org 2005-05-21
12:51 ---
Fixed for 4.0.0.
--
What|Removed |Added
Status|NEW |RESO
--- Additional Comments From dorit at il dot ibm dot com 2005-02-09 19:30
---
continued in this thread:
http://gcc.gnu.org/ml/gcc-patches/2005-02/msg00196.html
and cmmitted:
http://gcc.gnu.org/ml/gcc-cvs/2005-02/msg00153.html
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18441
--- Additional Comments From leehod at il dot ibm dot com 2005-01-19 19:28
---
There is now a patch addressing these issues.
See: http://gcc.gnu.org/ml/gcc-patches/2005-01/msg01247.html
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18441
--- Additional Comments From leehod at il dot ibm dot com 2004-12-22 18:59
---
I am working with Dorit on cleaning up the vectorizer dumps. We'd also like to
try to address this PR - here are some preliminary thoughts/questions:
1) The 'inform' utility doesn't look very suitable becaus
--- Additional Comments From dpatel at apple dot com 2004-12-13 20:16
---
Try -fdump-tree-vect-stats. It produces more user friendly output compared to
-details.
I am not fan of putting such diagnostics as part of warnings/info/errors.
IMO, we should enhance/
update -fdump-tree-vect
--- Additional Comments From pinskia at gcc dot gnu dot org 2004-11-12
02:45 ---
Confirmed, We should have done this by now but don't for reasons unknown to me.
We have all the
information we need as of right now.
--
What|Removed |Added
---
