https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93334
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93334
--- Comment #5 from N Schaeffer ---
Elaborating a bit on this:
I can eliminate this problem by using:
-O3 -fno-tree-loop-distribute-patterns -fno-tree-loop-vectorize
I wonder why -fno-tree-loop-distribute-patterns is not enough ?
In that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93334
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93334
--- Comment #3 from N Schaeffer ---
Hi,
Thanks for pointing out the issue about writing different values. This makes
sense.
However, since memset deals with bytes, whenever the type of array is floating
point data (or anything longer than
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93334
--- Comment #2 from bin cheng ---
(In reply to Richard Biener from comment #1)
> Confirmed. The issue is that the overlap would be an issue if the stores
> were using different values like
>
> void test_simple_code(long l, double* mem, long
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93334
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
