From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Aldy Hernandez <aldyh@redhat.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: PING: new pass to warn on questionable uses of alloca() and VLAs
Date: Wed, 27 Jul 2016 09:26:00 -0000 [thread overview]
Message-ID: <yddmvl3whxa.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <5798785F.8020001@redhat.com> (Aldy Hernandez's message of "Wed, 27 Jul 2016 05:01:19 -0400")
Hi Aldy,
> Just in case this got lost in noise, since I know there was a lot of back
> and forth between Martin Sebor and I.
>
> This is the last iteration.
>
> Tested on x86-64 Linux.
>
> OK for trunk?
>
> gcc/
>
> * Makefile.in (OBJS): Add gimple-ssa-warn-walloca.o.
> * passes.def: Add two instances of pass_walloca.
> * tree-pass.h (make_pass_walloca): New.
> * gimple-ssa-warn-walloca.c: New file.
just a nit: the files is called gimple-ssa-warn-alloca.[co].
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2016-07-27 9:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 9:01 Aldy Hernandez
2016-07-27 9:26 ` Rainer Orth [this message]
2016-08-04 16:38 ` Jeff Law
[not found] ` <57B6D2F1.6050709@redhat.com>
2016-08-19 14:57 ` Aldy Hernandez
2016-08-19 14:59 ` Aldy Hernandez
2016-09-13 20:30 ` Jeff Law
2016-10-18 21:42 ` Aldy Hernandez
2016-10-19 7:08 ` Eric Botcazou
2016-10-19 12:46 ` Aldy Hernandez
2016-10-19 13:24 ` Eric Botcazou
2016-10-19 13:27 ` Aldy Hernandez
2016-10-19 13:42 ` Eric Botcazou
2016-10-19 13:54 ` Aldy Hernandez
2016-10-19 15:32 ` Eric Botcazou
2016-10-19 10:45 ` Andreas Schwab
2016-10-19 10:50 ` Christophe Lyon
2016-10-19 12:54 ` Aldy Hernandez
2016-10-19 13:03 ` Andreas Schwab
2016-10-19 13:16 ` Eric Botcazou
2016-10-19 15:32 ` Aldy Hernandez
2016-10-19 15:38 ` Andreas Schwab
2016-10-19 15:42 ` Eric Botcazou
2016-10-19 15:55 ` Jeff Law
2016-10-19 16:22 ` Christophe Lyon
2016-10-19 18:43 ` Aldy Hernandez
2016-10-19 20:16 ` Christophe Lyon
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=yddmvl3whxa.fsf@CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=aldyh@redhat.com \
--cc=gcc-patches@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).