This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH]: New warning option -Walloca
On 31/08/2007, Raksit Ashok <raksit.ashok@gmail.com> wrote:
> > Manuel> On the contrary, I suppose it will work if you poison the identifier
> > Manuel> before including any system headers. Doesn't it?
> >
> > Tom> I believe this will give an error if a system header even declares
> > Tom> alloca. That's a bit unfriendly, since most users won't have control
> > Tom> over these headers.
>
> Yes, even declarations would cause an error:
I apologise for my ignorance but why does poison work like that?
> > Dave> Well, there's a thought: maybe poison should behave like warnings (i.e.
> > Dave> be suppressed for the most part) when it comes to system headers?
>
> This sounds like it would work too.
>
But then you won't get any warning when you use alloca through another
function or through a macro redefinition. Is that what you really
want?
Cheers,
Manuel.