search for: internchang

...be taught to respect the flag. 2. >void foo(char * restrict s1, char * restrict s2) { > printf(s1); > printf(s2); >} >If printf is argmemonly, then we could interchange the two printf calls. In this 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...

...;void foo(char * restrict s1, char * restrict s2) { > > printf(s1); > > printf(s2); > >} > > >If printf is argmemonly, then we could interchange the two printf calls. > > In this 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); > > >...

...> printf(s1); >>> > printf(s2); >>> >} >>> >>> >If printf is argmemonly, then we could interchange the two printf calls. >>> >>> In this 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); &gt...

...ar * restrict s2) { >> > printf(s1); >> > printf(s2); >> >} >> >> >If printf is argmemonly, then we could interchange the two printf calls. >> >> In this 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); >> > ... >>...

...> printf(s1); >>> > printf(s2); >>> >} >>> >>> >If printf is argmemonly, then we could interchange the two printf calls. >>> >>> In this 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); &gt...

...; >} >>>>> >>>>> >If printf is argmemonly, then we could interchange the two printf >>>>> calls. >>>>> >>>>> In this 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: >>>...