Summary: | Wrong code with gcc 4.0 tree-vectorizer | ||
---|---|---|---|
Product: | gcc | Reporter: | Michael Cieslinski <micis> |
Component: | tree-optimization | Assignee: | Ira Rosen <irar> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | gcc-bugs, irar |
Priority: | P2 | ||
Version: | 4.0.0 | ||
Target Milestone: | 4.0.0 | ||
Host: | x86_64-unknown-linux-gnu | Target: | x86_64-unknown-linux-gnu |
Build: | x86_64-unknown-linux-gnu | Known to work: | |
Known to fail: | Last reconfirmed: | 2005-03-02 12:43:57 |
Description
Michael Cieslinski
2005-02-21 16:16:25 UTC
I think this is related to PR 19716. Note the tree level looks correct to me. I found the problem that causes this. I'll send the patch next week. Ira After you found the problem, may I ask you to set the status NEW and target milestone to 4.0.0 ? That way this bug would show up in the list of open bugs for gcc40. Michael Cieslinski Ira, can you please remember to confirm bugs in Bugzilla when you find them? Micheal, this bug cannot be fixed in 4.0 since it is not a regression (the vectorizer is new). I would argue in favor of a new rule that allows to fix bugs in release branches for new features which are disabled by default, but for now this bug won't have a 4.0 milestone. Fixed in http://gcc.gnu.org/ml/gcc-patches/2005-02/msg01788.html. Waiting for review. I applied you patch and did a full bootstrap on x86_64. No new regressions. It fixes my problem. Michael Cieslinski The patch given in comment #5 seems to be included in gcc400 and in mainline. I think this PR should be closed. Michael Cieslinski |