From: Jeff Law Date: Mon, 27 Feb 1995 07:30:31 +0000 (-0700) Subject: pa.c (hppa_expand_prologue): Don't save the PIC register into the stack for functions... X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=9ccd072bd4c87ed02f4b955d9b71a99716d5ca6b;p=gcc.git pa.c (hppa_expand_prologue): Don't save the PIC register into the stack for functions which have no stack of... * pa.c (hppa_expand_prologue): Don't save the PIC register into the stack for functions which have no stack of their own. From-SVN: r9089 --- diff --git a/gcc/config/pa/pa.c b/gcc/config/pa/pa.c index 1b07661287c..e53949468df 100644 --- a/gcc/config/pa/pa.c +++ b/gcc/config/pa/pa.c @@ -2198,8 +2198,11 @@ hppa_expand_prologue() } /* The hppa calling conventions say that that %r19, the pic offset register, is saved at sp - 32 (in this function's frame) when - generating PIC code. */ - if (flag_pic) + generating PIC code. FIXME: What is the correct thing to do + for functions which make no calls and allocate no frame? Do + we need to allocate a frame, or can we just omit the save? For + now we'll just omit the save. */ + if (actual_fsize != 0 && flag_pic) store_reg (PIC_OFFSET_TABLE_REGNUM, -32, STACK_POINTER_REGNUM); /* Profiling code.