This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] Don't optimize stdarg functions if old-style builtins are used

From: Richard Henderson <rth at redhat dot com>
To: Jakub Jelinek <jakub at redhat dot com>
Cc: Eric Botcazou <ebotcazou at libertysurf dot fr>, gcc-patches at gcc dot gnu dot org
Date: Thu, 30 Sep 2004 10:01:41 -0700
Subject: Re: [PATCH] Don't optimize stdarg functions if old-style builtins are used
References: <20040927225032.GG31909@devserv.devel.redhat.com> <20040928223543.GD2339@redhat.com> <20040929204334.GT31909@devserv.devel.redhat.com> <200409301133.19471.ebotcazou@libertysurf.fr> <20040930114251.GX31909@devserv.devel.redhat.com>

On Thu, Sep 30, 2004 at 07:42:51AM -0400, Jakub Jelinek wrote:
> BTW, as sparc uses __builtin_saveregs () internally, I think a patch like
> this is needed, otherwise you would be in trouble if a function calls
> both __builtin_saveregs and __builtin_va_start.

I wouldn't worry about it.  Instead, transition sparc to 
TARGET_SETUP_INCOMING_VARARGS.

There aren't too many saveregs targets left.  If we can
get them transitioned away, we can remove __builtin_saveregs.

r~

References:
- [PATCH] Optimize stdarg functions
  - From: Jakub Jelinek
- Re: [PATCH] Optimize stdarg functions (take 2)
  - From: Richard Henderson
- [PATCH] Optimize stdarg functions with void * or char * va_list
  - From: Jakub Jelinek
- Re: [PATCH] Optimize stdarg functions with void * or char * va_list
  - From: Eric Botcazou
- [PATCH] Don't optimize stdarg functions if old-style builtins are used
  - From: Jakub Jelinek

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]