This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: When did -Wmaybe-unitialized make its appearance?
- From: Markus Trippelsdorf <markus at trippelsdorf dot de>
- To: Jeffrey Walton <noloader at gmail dot com>
- Cc: "gcc-help at gcc dot gnu dot org" <gcc-help at gcc dot gnu dot org>
- Date: Fri, 31 Jul 2015 10:51:40 +0200
- Subject: Re: When did -Wmaybe-unitialized make its appearance?
- Authentication-results: sourceware.org; auth=none
- References: <CAH8yC8k41KRc-Qq5WyKHs3QkqSe4druFTVA0WbJKSOBiyu_nrA at mail dot gmail dot com> <20150731082746 dot GA405 at x4> <CAH8yC8ndcZy6T3ZSr2nXvCxcYcguL0m2_ZyEXU+BWvf7z+LhhA at mail dot gmail dot com> <20150731084410 dot GB405 at x4> <CAH8yC8mAsxZ3KQG+TuYEqdrF4dNp88x88kGNOXsaCOuwg51-7w at mail dot gmail dot com>
On 2015.07.31 at 04:47 -0400, Jeffrey Walton wrote:
> On Fri, Jul 31, 2015 at 4:44 AM, Markus Trippelsdorf
> <markus@trippelsdorf.de> wrote:
> > On 2015.07.31 at 04:30 -0400, Jeffrey Walton wrote:
> >> >> When did -Wmaybe-unitialized make its appearance?
> >> >
> >> > The svn or git repositories are publicly available. They should give you
> >> > the answer.
> >>
> >> Would it be possible to start listing this information somewhere?
> >> Surely I'm not the only person who needs to know the intersection of
> >> features with versions.
> >
> > Instead of using gcc version checks for each feature, you could simply
> > use feature checks at configuration time.
> Thanks. There is no configuration time.
>
> The idea is you run it and things just work. It takes a little extra
> upfront work (like now) to save the headaches later.
Well, then look at how the Linux kernel does these checks without
configuration time. See e.g. cc-option in scripts/Kbuild.include.
--
Markus