[llvm-bugs] [Bug 28477] New: Some -Rpass-analysis=loop-vectorize diagnostics need rewording to include "loop not vectorized" prefix
via llvm-bugs
llvm-bugs at lists.llvm.org
Fri Jul 8 16:45:53 PDT 2016
https://llvm.org/bugs/show_bug.cgi?id=28477
Bug ID: 28477
Summary: Some -Rpass-analysis=loop-vectorize diagnostics need
rewording to include "loop not vectorized" prefix
Product: new-bugs
Version: trunk
Hardware: Macintosh
OS: MacOS X
Status: NEW
Severity: normal
Priority: P
Component: new bugs
Assignee: unassignedbugs at nondot.org
Reporter: sean at rogue-research.com
CC: llvm-bugs at lists.llvm.org
Classification: Unclassified
Usually clang will output something pretty clear like:
"remark: loop not vectorized: loop control flow is not understood by vectorizer
[-Rpass-analysis=loop-vectorize]"
Other times I'll see:
"remark: the cost-model indicates that interleaving is not beneficial
[-Rpass-analysis=loop-vectorize]"
Adam Nemet confirmed to me on cfe-dev that it's indeed meaning to say that the
loop was *not* vectorized. This would be much clearer if the text included
"loop not vectorized" like the other messages.
--
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20160708/e84d8dae/attachment.html>
More information about the llvm-bugs
mailing list