https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108715
--- Comment #15 from Andrew Pinski ---
(In reply to Jakub Jelinek from comment #14)
> It isn't really a dup, that other PR is about strlen pattern in some
> function with a different name.
PR 103858 was also marked as a dup much earlier.
I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108715
--- Comment #14 from Jakub Jelinek ---
It isn't really a dup, that other PR is about strlen pattern in some function
with a different name.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108715
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108715
--- Comment #12 from Jakub Jelinek ---
While the strlen pattern recognition has been added later than memcpy/memset,
it is really the same thing. With -ffreestanding which you are supposed to use
when you are providing C library yourself (or
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108715
--- Comment #11 from Daniel Zaoui ---
I checked on GCC 5.2.0 and 10.2 (RISC-V toolchain) and it doesn't happen.
I didn't understand what is the conclusion for the duplicate tickets. In
107415, it seems to be an expected behavior. Although I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108715
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108715
--- Comment #9 from Daniel Zaoui ---
(In reply to Andrew Pinski from comment #8)
> There is a dup of this bug already filed. And a related bug when defining
> "memcpy" too.
>
> C is special.
Do you have any bug ID? I searched before opening
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108715
Andrew Pinski changed:
What|Removed |Added
Component|c |middle-end
--- Comment #8 from Andrew
