On Tue, Apr 5, 2016 at 2:45 AM, Umesh Kalappa wrote:
> I need to ,make the changes only to the function args(varargs),hence
> making the changes in TARGET_PROMOTE_FUNCTION_MODE will do ?.
If TARGET_PROMOTE_FUNCTION_MODE disagrees with PROMOTE_MODE, it is
possible that the middle end may generat
Thank you Jim for the input,
I need to ,make the changes only to the function args(varargs),hence
making the changes in TARGET_PROMOTE_FUNCTION_MODE will do ?.
one more question ,i do have defined the TARGET_PROMOTE_FUNCTION_MODE
(arm.c) and cross compilling for aarch64 ,but still gcc calls
def
On 04/04/2016 08:55 AM, Umesh Kalappa wrote:
We are in process of changing the gcc compiler for aarch64 abi ,w.r.t
varargs function arguments handling.
default(LP64) ,where 1,2,4 bytes args are promoted to word size i.e 4
bytes ,we need to change these behaviour to 8 bytes (double word).
we a
Hi All,
We are in process of changing the gcc compiler for aarch64 abi ,w.r.t
varargs function arguments handling.
default(LP64) ,where 1,2,4 bytes args are promoted to word size i.e 4
bytes ,we need to change these behaviour to 8 bytes (double word).
we are looking both hooks like PROMOTE_MO