On Wed, 9 Jan 2013, Ondřej Bílka wrote:
gcc currently does not even optimize following fragment:int foo(){ char *x=malloc(64); free(x); }
Yes it does. (not that more optimizations aren't possible, but it does this one) -- Marc Glisse
On Wed, 9 Jan 2013, Ondřej Bílka wrote:
gcc currently does not even optimize following fragment:int foo(){ char *x=malloc(64); free(x); }
Yes it does. (not that more optimizations aren't possible, but it does this one) -- Marc Glisse