search for: almostargmemonly

...be modified according to the diff in the first mail >> > in this email thread. >> >> > The alternative approach that was discussed would involve the >> > following changes: >> >> > (Approach B) >> > 1. Define new attributes AlmostReadNone and AlmostArgMemOnly, (with >> > the "Almost" part denoting that the function may accesses globals >> > that are not part of the IR). >> > 2. malloc/free would have AlmostReadNone set and printf would have >> > AlmostArgMemOnly set ... (and similarly other libc calls). >...

...make sure it isn't > present. > 6. GlobalsAA will be modified according to the diff in the first mail > in this email thread. > The alternative approach that was discussed would involve the > following changes: > (Approach B) > 1. Define new attributes AlmostReadNone and AlmostArgMemOnly, (with > the "Almost" part denoting that the function may accesses globals > that are not part of the IR). > 2. malloc/free would have AlmostReadNone set and printf would have > AlmostArgMemOnly set ... (and similarly other libc calls). > 3. In the diff I originally posted...

----- Original Message ----- > From: "Joseph Tremoulet" <jotrem at microsoft.com> > To: "Hal Finkel" <hfinkel at anl.gov>, "Mehdi Amini" <mehdi.amini at apple.com> > Cc: "llvm-dev" <llvm-dev at lists.llvm.org> > Sent: Friday, December 11, 2015 3:35:38 PM > Subject: RE: [llvm-dev] RFC: New function attribute

...lag and make sure it isn't present. > 6. GlobalsAA will be modified according to the diff in the first mail in this email thread. > > The alternative approach that was discussed would involve the following changes: > (Approach B) > 1. Define new attributes AlmostReadNone and AlmostArgMemOnly, (with the "Almost" part denoting that the function may > accesses globals that are not part of the IR). > 2. malloc/free would have AlmostReadNone set and printf would have AlmostArgMemOnly set ... (and similarly other libc > calls). > 3. In the diff I originally posted f...