From: Ian Lance Taylor <iant@google.com>
To: Janboe Ye <yuan-bo.ye@motorola.com>
Cc: gcc@gcc.gnu.org, janboe.ye@gmail.com
Subject: Re: how to use expand_builtin_alloca
Date: Mon, 13 Jul 2009 21:17:00 -0000 [thread overview]
Message-ID: <m37hycwads.fsf@google.com> (raw)
In-Reply-To: <1247519293.4414.16.camel@debian-nb> (Janboe Ye's message of "Mon\, 13 Jul 2009 16\:08\:13 -0500")
Janboe Ye <yuan-bo.ye@motorola.com> writes:
> normally gcc will use expand_builtin_alloca to handle variable array.
> But mudflap will force this function to return immediately to invoke
> alloca explicit.
>
> Is there some way to still use expand_builtin_alloca without changing
> gcc source code?
mudflap can't check accesses to memory allocated using alloca unless it
overrides __builtin_alloca. So if I understand your question correctly,
the answer is no. Although, of course, you could simply not use mudflap
for the code in question.
Ian
next prev parent reply other threads:[~2009-07-13 21:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-13 21:08 Janboe Ye
2009-07-13 21:17 ` Ian Lance Taylor [this message]
2009-07-13 21:27 ` Janboe Ye
2009-07-13 21:39 ` Ian Lance Taylor
2009-07-16 22:32 ` Frank Ch. Eigler
2009-07-19 20:08 ` ye janboe
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=m37hycwads.fsf@google.com \
--to=iant@google.com \
--cc=gcc@gcc.gnu.org \
--cc=janboe.ye@gmail.com \
--cc=yuan-bo.ye@motorola.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).