public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/91972] Bootstrap should use -Wmissing-declarations
Date: Sun, 10 Sep 2023 15:34:04 +0000 [thread overview]
Message-ID: <bug-91972-4-AEguYqD5Zm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-91972-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91972
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|easyhack |
--- Comment #9 from Eric Gallager <egallager at gcc dot gnu.org> ---
so, I've tried enabling this flag while building, and one problem with it is
that GCC's genfoo machinery for its garbage collection system creates a bunch
of gt-*.h headers with a bunch of autogenerated gt_ggc_mx and gt_pch_nx
functions in them that all get warned about... this will require messing with
the generator utilities to get them to stop generating code that warns, so this
will be more difficult than I thought; removing the "easyhack" keyword...
prev parent reply other threads:[~2023-09-10 15:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-91972-4@http.gcc.gnu.org/bugzilla/>
2020-05-05 9:42 ` amonakov at gcc dot gnu.org
2020-05-05 13:24 ` redi at gcc dot gnu.org
2020-05-05 13:34 ` rguenth at gcc dot gnu.org
2020-05-05 14:01 ` amonakov at gcc dot gnu.org
2020-06-08 1:55 ` egallager at gcc dot gnu.org
2021-11-30 7:18 ` egallager at gcc dot gnu.org
2021-11-30 10:38 ` amonakov at gcc dot gnu.org
2021-11-30 11:48 ` egallager at gcc dot gnu.org
2023-09-10 15:34 ` egallager at gcc dot gnu.org [this message]
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=bug-91972-4-AEguYqD5Zm@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).