From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
To: rth@redhat.com
Cc: gcc@gcc.gnu.org
Subject: Re: Using alloca (or stmt exprs) as a function call argument is bad?
Date: Sun, 23 Sep 2001 07:55:00 -0000 [thread overview]
Message-ID: <200109231455.KAA17155@caip.rutgers.edu> (raw)
> From: Richard Henderson <rth@redhat.com>
>
> On Mon, Sep 17, 2001 at 02:31:06PM -0400, Kaveh R. Ghazi wrote:
> > And its presumably because alloca is diddling with
> > the stack at the same time function parameters are being pushed there?
>
> Yes.
> r~
So have you any thoughts on how best to have gcc warn the user that
they've just done something dangerous?
E.g. gcc/c-typeck.c:error_init() line 4594...
I'd like to automate finding these cases.
--
Kaveh R. Ghazi Engagement Manager / Project Services
ghazi@caip.rutgers.edu Qwest Internet Solutions
next reply other threads:[~2001-09-23 7:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-23 7:55 Kaveh R. Ghazi [this message]
2001-09-24 12:45 ` Richard Henderson
-- strict thread matches above, loose matches on Subject: below --
2001-09-24 15:43 Kaveh R. Ghazi
2001-09-24 15:46 ` Richard Henderson
2001-09-25 6:38 ` Jan Hubicka
2001-09-17 11:31 Kaveh R. Ghazi
2001-09-17 15:50 ` Richard Henderson
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=200109231455.KAA17155@caip.rutgers.edu \
--to=ghazi@caip.rutgers.edu \
--cc=gcc@gcc.gnu.org \
--cc=rth@redhat.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).