This is the mail archive of the
mailing list for the GCC project.
Re: warning message control: check for enabled warnings
- From: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>
- To: dj at redhat dot com
- Cc: gcc-patches at gcc dot gnu dot org, rth at redhat dot com
- Date: Mon, 2 May 2005 18:15:39 -0400 (EDT)
- Subject: Re: warning message control: check for enabled warnings
- References: <200504230001.j3N01RR8016620@greed.delorie.com> <4269966E.email@example.com> <200504230039.j3N0dWvp017120@greed.delorie.com> <4269A6B7.firstname.lastname@example.org> <200504232138.j3NLcscP001625@greed.delorie.com> <200504252153.j3PLr5X9026266@greed.delorie.com> <200504292255.j3TMtSFY013487@greed.delorie.com> <20050429230150.GA8858@redhat.com> <200504292311.j3TNBQ2N014116@greed.delorie.com> <200504300340.XAA03654@caipclassic.rutgers.edu> <200505021758.j42Hwqcs032365@greed.delorie.com>
> > Doesn't the naked zero yield a sentinel warning during bootstrap and
> > die from -Werror?
> I was pretty sure I'd enabled those warnings/errors when I configured
> (a full bootstrap is too long for incremental development, but I do
> try to re-bootstrap before commits like that) but it seems to have
> eluded me. Sorry.
Ah, you didn't do a full bootstrap. In that case, you wouldn't see
the warning unless the bootstrap compiler was 4.0 or mainline. (The
sentinel warning was added in 4.0.) Once you do a full bootstrap it
should bite, I'd be interested to know either way. :-)
Kaveh R. Ghazi email@example.com