[Bug tree-optimization/62112] Optimize out malloc when block is unused or write-only

2014-08-21 Thread glisse at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62112 Marc Glisse changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug tree-optimization/62112] Optimize out malloc when block is unused or write-only

2014-08-21 Thread glisse at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62112 --- Comment #5 from Marc Glisse --- Author: glisse Date: Thu Aug 21 09:32:21 2014 New Revision: 214262 URL: https://gcc.gnu.org/viewcvs?rev=214262&root=gcc&view=rev Log: 2014-08-21 Marc Glisse PR tree-optimization/62112 gcc/ * gimple

[Bug tree-optimization/62112] Optimize out malloc when block is unused or write-only

2014-08-16 Thread glisse at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62112 Marc Glisse changed: What|Removed |Added CC||glisse at gcc dot gnu.org --- Comment #4 f

[Bug tree-optimization/62112] Optimize out malloc when block is unused or write-only

2014-08-13 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62112 Richard Biener changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug tree-optimization/62112] Optimize out malloc when block is unused or write-only

2014-08-12 Thread zackw at panix dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62112 --- Comment #2 from Zack Weinberg --- I observe that the `memcpy` does get lowered to inline code. Is it just a phase-ordering problem that we then don't detect the stores as dead?

[Bug tree-optimization/62112] Optimize out malloc when block is unused or write-only

2014-08-12 Thread glisse at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62112 --- Comment #1 from Marc Glisse --- Main issue here is that DSE only applies to assignments and not function calls like memcpy (there must be a few dups somewhere), so we never remove memcpy, even if we call free(x);free(y); afterwards. With a fo