search for: really_big

...example too, printf maintains an internal state, preventing the calls from being internchanged. Also, it is now correct to add ArgMemOnly to printf as it does not access any other program memory. 3. >For malloc this is still a problem, in the following sense, if we have: > > p1 = malloc(really_big); > ... > free(p1); > > p2 = malloc(really_big); > ... > free(p2); >allowing a transformation into: > p1 = malloc(really_big); > p2 = malloc(really_big); > ... > free(p1); free(p2); >could be problematic. Both free and malloc would be marked with hav...

...internal state, preventing the > calls from being internchanged. Also, it is now correct to add ArgMemOnly > to printf as it does not access any other program memory. > > 3. > >For malloc this is still a problem, in the following sense, if we have: > > > > p1 = malloc(really_big); > > ... > > free(p1); > > > > p2 = malloc(really_big); > > ... > > free(p2); > >allowing a transformation into: > > p1 = malloc(really_big); > > p2 = malloc(really_big); > > ... > > free(p1); free(p2); > >could be...

...eing internchanged. Also, it is now correct to add >>> ArgMemOnly to printf as it does not access any other program memory. >>> >>> 3. >>> >For malloc this is still a problem, in the following sense, if we have: >>> > >>> > p1 = malloc(really_big); >>> > ... >>> > free(p1); >>> > >>> > p2 = malloc(really_big); >>> > ... >>> > free(p2); >>> >allowing a transformation into: >>> > p1 = malloc(really_big); >>> > p2 = malloc(really_...

...he >> calls from being internchanged. Also, it is now correct to add >> ArgMemOnly to printf as it does not access any other program memory. >> >> 3. >> >For malloc this is still a problem, in the following sense, if we have: >> > >> > p1 = malloc(really_big); >> > ... >> > free(p1); >> > >> > p2 = malloc(really_big); >> > ... >> > free(p2); >> >allowing a transformation into: >> > p1 = malloc(really_big); >> > p2 = malloc(really_big); >> > ... >>...

...eing internchanged. Also, it is now correct to add >>> ArgMemOnly to printf as it does not access any other program memory. >>> >>> 3. >>> >For malloc this is still a problem, in the following sense, if we have: >>> > >>> > p1 = malloc(really_big); >>> > ... >>> > free(p1); >>> > >>> > p2 = malloc(really_big); >>> > ... >>> > free(p2); >>> >allowing a transformation into: >>> > p1 = malloc(really_big); >>> > p2 = malloc(really_...

...t; ArgMemOnly to printf as it does not access any other program memory. >>>>> >>>>> 3. >>>>> >For malloc this is still a problem, in the following sense, if we >>>>> have: >>>>> > >>>>> > p1 = malloc(really_big); >>>>> > ... >>>>> > free(p1); >>>>> > >>>>> > p2 = malloc(really_big); >>>>> > ... >>>>> > free(p2); >>>>> >allowing a transformation into: >>>>> >...

----- Original Message ----- > From: "James Molloy via llvm-dev" <llvm-dev at lists.llvm.org> > To: "Vaivaswatha Nagaraj" <vn at compilertree.com> > Cc: "LLVM Dev" <llvm-dev at lists.llvm.org> > Sent: Thursday, December 3, 2015 4:41:46 AM > Subject: Re: [llvm-dev] Function attributes for LibFunc and its impact on GlobalsAA > >