On 10/13/14 04:48, Ilya Enkovich wrote:
--
2014-10-13 Ilya Enkovich
* ipa-chkp.c: New.
* ipa-chkp.h: New.
* Makefile.in (OBJS): Add ipa-chkp.o.
* c-family/c-common.c (c_common_attribute_table): Fix documentation.
(c_common_format_attribute_table): Likew
On 10 Oct 13:14, Jeff Law wrote:
> On 10/08/14 12:55, Ilya Enkovich wrote:
> >Hi,
> >
> >This patch introduces two IPA passes used by Pointer Bounds Checker. One
> >pass creates clones for instrumentation. The other one transforms unneeded
> >functions into thunks.
> >
> >Thanks,
> >Ilya
> >--
On 10/08/14 12:55, Ilya Enkovich wrote:
Hi,
This patch introduces two IPA passes used by Pointer Bounds Checker. One pass
creates clones for instrumentation. The other one transforms unneeded
functions into thunks.
Thanks,
Ilya
--
2014-10-08 Ilya Enkovich
* ipa-chkp.c: New.
2014-10-09 2:40 GMT+04:00 Jan Hubicka :
>>
>> I prevent clone's body from removal and therefore original should call
>> clone (otherwise clone may have no callers and be removed). I think
>> call edge may work (need to recall other cases when reference do its
>> work) but is it OK to have call wit
>
> I prevent clone's body from removal and therefore original should call
> clone (otherwise clone may have no callers and be removed). I think
> call edge may work (need to recall other cases when reference do its
> work) but is it OK to have call with no stmt for non thunk nodes?
OK, I guess
> 2014-10-08 23:41 GMT+04:00 Jan Hubicka :
> >> +/* Pointer Bounds Checker has two IPA passes to support code
> >> instrumentation.
> >> +
> >> +In instrumented code each pointer is provided with bounds. For input
> >> +pointer parameters it means we also have bounds passed. For calls i
2014-10-08 23:41 GMT+04:00 Jan Hubicka :
>> +/* Pointer Bounds Checker has two IPA passes to support code
>> instrumentation.
>> +
>> +In instrumented code each pointer is provided with bounds. For input
>> +pointer parameters it means we also have bounds passed. For calls it
>> +me
> +/* Pointer Bounds Checker has two IPA passes to support code
> instrumentation.
> +
> +In instrumented code each pointer is provided with bounds. For input
> +pointer parameters it means we also have bounds passed. For calls it
> +means we have additional bounds arguments for poi
