public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/15450] Ability to turn selected warnings into errors. Date: Fri, 31 Mar 2023 11:38:09 +0000 [thread overview] Message-ID: <bug-15450-4-P8qJ6PcxZP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-15450-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=15450 --- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Note for long long, you can use -Wno-long-long which is documented here: https://gcc.gnu.org/onlinedocs/gcc-12.2.0/gcc/Warning-Options.html#index-Wlong-long Been around since 3.1: https://gcc.gnu.org/onlinedocs/gcc-3.1.1/gcc/Warning-Options.html#Warning%20Options -Wlong-long Warn if long long type is used. This is default. To inhibit the warning messages, use -Wno-long-long. Flags -Wlong-long and -Wno-long-long are taken into account only when -pedantic flag is used.
next parent reply other threads:[~2023-03-31 11:38 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-15450-4@http.gcc.gnu.org/bugzilla/> 2023-03-31 11:38 ` pinskia at gcc dot gnu.org [this message] [not found] <20040514231716.15450.nick@reloco.com.ar> 2004-05-15 18:19 ` pinskia at gcc dot gnu dot org 2004-05-16 19:03 ` nick at reloco dot com dot ar
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-15450-4-P8qJ6PcxZP@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: linkBe 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).