From: Ralf Baechle <ralf@uni-koblenz.de>
To: "MEHTA,HIREN (A-SanJose,ex1)" <hiren_mehta@agilent.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: __builtin_* functions
Date: Sun, 11 Nov 2001 08:55:26 +1100 [thread overview]
Message-ID: <20011111085526.A13304@dea.linux-mips.net> (raw)
In-Reply-To: <01A7DAF31F93D511AEE300D0B706ED9208E4CA@axcs13.cos.agilent.com>
In-Reply-To: <01A7DAF31F93D511AEE300D0B706ED9208E4CA@axcs13.cos.agilent.com>; from hiren_mehta@agilent.com on Thu, Nov 08, 2001 at 11:19:40AM -0700
On Thu, Nov 08, 2001 at 11:19:40AM -0700, MEHTA,HIREN (A-SanJose,ex1) wrote:
> Can these __builtin_* functions provided by gcc be used inside kernel ?
> In particular __builtin_alloca ?
In theory they're usable, in practice you should consider that alloca will
allocate memory on the stack which is of very limited size under Linux so
alloca doesn't usually seem to be a good idea.
Ralf
prev parent reply other threads:[~2001-11-11 1:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-08 18:19 __builtin_* functions MEHTA,HIREN (A-SanJose,ex1)
2001-11-10 21:55 ` Ralf Baechle [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20011111085526.A13304@dea.linux-mips.net \
--to=ralf@uni-koblenz.de \
--cc=hiren_mehta@agilent.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox