Hi, Frank
>Those in turn
>might be represented with almost the normal mf_xform_decls(), while
>letting __builtin_alloca() remain.
How can we just remain __builtin_alloca() only for variable-length array?
Mudflap changes expand_builtin_alloca function.
I think it is enough for apply mudflap in Linu
> Janboe Ye writes:
>> normally gcc will use expand_builtin_alloca to handle variable array.
>> But mudflap will force this function to return immediately to invoke
>> alloca explicit.
>>
>> Is there some way to still use expand_builtin_alloca without changing
>> gcc source code?
I don't think
Janboe Ye writes:
> Is it possible to override alloc to do the same thing as
> expand_buitlin_alloca in application codes?
I don't know of any way to do that when using mudflap. If there were
such a way, it would imply that mudflap were broken, or that there is a
special way to work around it.
Hi Ian
Thanks for reply.
Is it possible to override alloc to do the same thing as
expand_buitlin_alloca in application codes?
On Mon, 2009-07-13 at 14:17 -0700, Ian Lance Taylor wrote:
> Janboe Ye writes:
>
> > normally gcc will use expand_builtin_alloca to handle variable array.
> > But mud
Janboe Ye writes:
> normally gcc will use expand_builtin_alloca to handle variable array.
> But mudflap will force this function to return immediately to invoke
> alloca explicit.
>
> Is there some way to still use expand_builtin_alloca without changing
> gcc source code?
mudflap can't check acc
Hi,
normally gcc will use expand_builtin_alloca to handle variable array.
But mudflap will force this function to return immediately to invoke
alloca explicit.
Is there some way to still use expand_builtin_alloca without changing
gcc source code?
Thanks a lot!
Janboe Ye
