From: <Paul_Koning@Dell.com>
To: <gdb@sourceware.org>
Subject: Why pedantic?
Date: Mon, 24 Aug 2015 18:15:00 -0000 [thread overview]
Message-ID: <F7BDA5B1-D300-42DB-968F-C4AEBFA880C2@dell.com> (raw)
I'm trying to understand why --pedantic is specified in several of the subdirectories used with building gdb -- and in particular, why there isn't any obvious way to turn that off. I've run into this in "libiberty" and possibly also "libdecnumber". While this may be ok for Linux, it breaks some cross-builds. At the very least I end up having to work around a pile of "C90 doesn't support blah blah" messages that now need to go into the "ignore this warning during builds" list in my build procedures.
"pedantic" generally defines warnings that are suggested by the standard but are judged to be not particularly useful -- so why use them unconditionally?
paul
next reply other threads:[~2015-08-24 18:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-24 18:15 Paul_Koning [this message]
2015-08-25 10:05 ` Pedro Alves
2015-08-25 12:52 ` Paul_Koning
2015-08-25 13:05 ` Andreas Schwab
2015-08-25 13:17 ` Paul_Koning
2015-08-25 13:41 ` Pedro Alves
2015-08-25 13:44 ` Andreas Schwab
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=F7BDA5B1-D300-42DB-968F-C4AEBFA880C2@dell.com \
--to=paul_koning@dell.com \
--cc=gdb@sourceware.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