On Wed, Jan 9, 2013 at 5:33 PM, Ondřej Bílka wrote:
> On Wed, Jan 09, 2013 at 05:12:06PM +0100, Marc Glisse wrote:
>> 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 i
On Wed, Jan 09, 2013 at 05:12:06PM +0100, Marc Glisse wrote:
> 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
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
