public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: ballsystemlord <doark@mail.com>
To: gcc-help@gcc.gnu.org
Subject: Re: A few Qs on the -Wfoo options
Date: Tue, 17 Dec 2013 17:39:00 -0000	[thread overview]
Message-ID: <1387301988872-996338.post@n5.nabble.com> (raw)
In-Reply-To: <CAKOQZ8y2rQuXwJSPw4_jqTmFhbsxNhVWaDmtg_i6smP-qwChvg@mail.gmail.com>

Ok, I've reread them. I could not find the definition of some of them because
they are only mentioned int the info manual under their '--no-'
counterparts, so when I searched for them with grep (because I did not
remember seeing them before because they were not there,) nothing came up.
I'm still interested in learning a little more about a few though.

-Wimplicit-interface               What's an explicit interface?
-Wimplicit-procedure             What's an explicit interface?
-Winvalid-memory-model      I could not find it mentioned in the info
manual.
-Wcharacter-truncation         "Warn when a character assignment will
truncate the assigned string." How can a string be truncated?
-Wlogical-op                        Why would it give false positives?
What's the criteria under which it makes these assumptions?
-Wstack-protector                 How can a function get smashed?




--
View this message in context: http://gcc.1065356.n5.nabble.com/A-few-Qs-on-the-Wfoo-options-tp987688p996338.html
Sent from the gcc - Help mailing list archive at Nabble.com.

  reply	other threads:[~2013-12-17 17:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-20 19:48 ballsystemlord
2013-11-21  7:24 ` Ian Lance Taylor
2013-12-17 17:39   ` ballsystemlord [this message]
2013-12-17 17:43   ` ballsystemlord
2013-12-30 21:48 ` ballsystemlord
     [not found] <52B0FB85.3040604@gmail.com>
2013-12-18 19:48 ` Ángel González

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=1387301988872-996338.post@n5.nabble.com \
    --to=doark@mail.com \
    --cc=gcc-help@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).