This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc 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: Policy: alloca vs. malloc?

From: Paul Eggert <eggert at cs dot ucla dot edu>
To: Siddhesh Poyarekar <siddhesh dot poyarekar at gmail dot com>
Cc: Carlos O'Donell <carlos_odonell at mentor dot com>, libc-alpha <libc-alpha at sourceware dot org>,Jakub Jelinek <jakub at redhat dot com>
Date: Thu, 07 Jun 2012 23:40:44 -0700
Subject: Re: Policy: alloca vs. malloc?
References: <4FD0E4DC.1000105@mentor.com> <CAAHN_R1pNNXxgNi1fJZOeBA_urafVh2ApM1ni8NReSgHjrX0LA@mail.gmail.com> <4FD19AB7.2020200@cs.ucla.edu> <CAAHN_R0cNn=iQLMSRrfLkmbo8dCTuxKrg5F9wpLrOeV_Qj2=Dw@mail.gmail.com>

On 06/07/2012 11:38 PM, Siddhesh Poyarekar wrote:
>     Use of {{{alloca}}} is a memory optimization compared to having a
> local array on stack..

Thanks, I've included that wording in the wiki.

References:
- Policy: alloca vs. malloc?
  - From: Carlos O'Donell
- Re: Policy: alloca vs. malloc?
  - From: Siddhesh Poyarekar
- Re: Policy: alloca vs. malloc?
  - From: Paul Eggert
- Re: Policy: alloca vs. malloc?
  - From: Siddhesh Poyarekar

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