http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58686
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
CC| |rakdver at gcc dot gnu.org,
| |rguenth at gcc dot gnu.org
Blocks| |53947
Summary|[BUG] |vect_get_loop_niters()
|vect_get_loop_niters() |fails for some loops
|cound not get the correct |
|result for some loops. |
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
You mention several things that sound like they may lead to wrong code. Based
on your analysis, can you construct testcases that show a miscompile? Easiest
would be to trick niter analysis to think a loop runs just once so it is
peeled completely.
Best have different bugreports for the (possible) wrong-code issues as this
bug starts about a missed optimization. [versioning for niter may be
a possible solution, in case we can build proper conditions in
niter->assumptions]
