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] Avoid using alloca for stack_usage_map if argument size is excessively large

From: Andrew Pinski <pinskia at physics dot uc dot edu>
To: Jakub Jelinek <jakub at redhat dot com>
Cc: gcc-patches at gcc dot gnu dot org
Date: Wed, 22 Jun 2005 08:06:51 -0400
Subject: Re: [PATCH] Avoid using alloca for stack_usage_map if argument size is excessively large
References: <20050622093305.GA7663@sunsite.mff.cuni.cz>

On Jun 22, 2005, at 5:33 AM, Jakub Jelinek wrote:

Hi!

GCC will not compile programs that pass excessively large arguments
by value, because it uses alloca unconditionally for stack_usage_map,
no matter how big the arguments are.
It is true that for running such program you need to increase
stack limits, but programs aren't necessarily compiled on the same
system as they are run on, so IMHO using xmalloc/free for really big
argument sizes certainly doesn't hurt.  256K is a random number, on the
other side making it --param sounds overkill to me.
Ok for HEAD?

This is PR 17965.

Thanks,
Andrew Pinski

References:
- [PATCH] Avoid using alloca for stack_usage_map if argument size is excessively large
  - From: Jakub Jelinek

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