https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79697
Martin Sebor changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79697
--- Comment #8 from prathamesh3492 at gcc dot gnu.org ---
Author: prathamesh3492
Date: Sat Apr 29 10:05:13 2017
New Revision: 247407
URL: https://gcc.gnu.org/viewcvs?rev=247407&root=gcc&view=rev
Log:
2017-04-29 Prathamesh Kulkarni
PR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79697
--- Comment #7 from Peter Bergner ---
(In reply to Marc Glisse from comment #6)
> * malloc, strdup, etc are not pure!
Ahh, of course not. Nevermind. :-)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79697
--- Comment #6 from Marc Glisse ---
(In reply to Peter Bergner from comment #5)
> Why do we have to special case these functions? Why can't we do this for
> all functions that are marked as const/pure, since we know they have no side
> effects o
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79697
Peter Bergner changed:
What|Removed |Added
CC||bergner at gcc dot gnu.org
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79697
prathamesh3492 at gcc dot gnu.org changed:
What|Removed |Added
CC||prathamesh3492 at gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79697
--- Comment #3 from Andrew Pinski ---
It makes sense to convert realloc(0, n) to just malloc and the rest just works.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79697
Martin Sebor changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79697
--- Comment #1 from Martin Sebor ---
Ditto for __builtin_strdup and __builtin_strndup. Both of those calls can (and
arguably should) be eliminated. If they're not eliminated (but even if they
are) a warning on them can and arguably should be is
