This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH]: New warning option -Walloca


"Raksit Ashok" <raksit.ashok@gmail.com> writes:

> On 17 Sep 2007 17:03:43 -0700, Ian Lance Taylor <iant@google.com> wrote:
> > DJ Delorie <dj@redhat.com> writes:
> >
> > > "Raksit Ashok" <raksit.ashok@gmail.com> writes:
> > > > Following your advice, Dave, I have implemented a more general
> > > > warning: -Wdisallowed-function-list=foo,bar,alloca,... : emit warning
> > > > on calls to these functions.
> > >
> > > What about -Werror-disallowed-functions-list=... ?  That makes it act
> > > like all (most?) of the other -W options.
> >
> > It seems to me that most of the -W options support -Werror=foo to turn
> > them into an error.  By analogy, -Werror=disallowed-functions-list
> > should turn the warning into an error.  I'm not sure what
> > -Werror-disallowed-functions-list would do.
> >
> > Ian
> >
> 
> More precisely, "-Werror=disallowed-functions-list=" (with the equals
> sign at the end) would turn the new warning into error. Does this
> sound reasonable?

Well, I don't like the trailing '=' so much myself.  I don't think
typical users will be able to figure that out.

Ian


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]