From: "Martin v. Loewis" <martin@loewis.home.cs.tu-berlin.de>
To: zbabar@luminousnetworks.com
Cc: gcc-help@gcc.gnu.org
Subject: Re: gcc warnings
Date: Wed, 24 May 2000 23:48:00 -0000 [thread overview]
Message-ID: <200005250638.IAA01194@loewis.home.cs.tu-berlin.de> (raw)
In-Reply-To: <090825D1E60BD311B8390090276D5C492CA0FE@GALILEO>
> I need some resource on the warnings and errors that gcc generates and I
> wonder if there is some literature available listing all the warnings and
> their probable causes. Actually I've been asked to debug some C project
> files and since I'm a newbie to C therefore most of the warnings generated
> by gcc during compilation escape me.
Please have a look at the section "Warning Options" in the gcc manual.
Regards,
Martin
next prev parent reply other threads:[~2000-05-24 23:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-24 14:29 Zia Babar
2000-05-24 23:48 ` Martin v. Loewis [this message]
2007-10-17 9:08 Humpolicek, Jiri - Acision
2007-10-17 11:48 ` John Love-Jensen
2007-10-17 11:49 ` Tom St Denis
2007-10-17 14:08 ` Humpolicek, Jiri - Acision
2007-10-17 13:28 ` Tim Prince
2007-10-17 14:28 ` Humpolicek, Jiri - Acision
2007-10-17 15:25 ` Andrew Haley
2008-08-12 15:36 kamelopardus
2008-08-12 15:48 ` Andrew Bell
2008-08-12 15:52 ` Joel Dice
2008-08-12 17:19 ` kamelopardus
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=200005250638.IAA01194@loewis.home.cs.tu-berlin.de \
--to=martin@loewis.home.cs.tu-berlin.de \
--cc=gcc-help@gcc.gnu.org \
--cc=zbabar@luminousnetworks.com \
/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).