public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/101385] -Werror doesn't have effect on Ada frontend
Date: Fri, 09 Jul 2021 15:51:15 +0000 [thread overview]
Message-ID: <bug-101385-4-1B17jJR6jP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101385-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101385
--- Comment #3 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> I see in the gnat_ugn manual that there is still the -Werror option that
> causes GCC back end to treat warnings as errors. Is that means -gnatwe is
> for front end, and -Werror for back end?
Yes, the -gnatw switches are for the front-end and the -W switches for the
back-end, but we'll make -Werror imply -gnatwe in a future release.
next prev parent reply other threads:[~2021-07-09 15:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-09 10:20 [Bug ada/101385] New: " mytbk920423 at gmail dot com
2021-07-09 10:34 ` [Bug ada/101385] " ebotcazou at gcc dot gnu.org
2021-07-09 11:58 ` mytbk920423 at gmail dot com
2021-07-09 15:51 ` ebotcazou at gcc dot gnu.org [this message]
2021-07-09 15:51 ` ebotcazou at gcc dot gnu.org
2021-09-14 8:33 ` cvs-commit at gcc dot gnu.org
2021-09-14 8:35 ` ebotcazou at gcc dot gnu.org
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-101385-4-1B17jJR6jP@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).