public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Eus <eus@member.fsf.org>
To: Kastil <lordgalloth@gmail.com>
Cc: GCC Help Mailing List <gcc-help@gcc.gnu.org>
Subject: Re: Description warnings
Date: Sat, 02 Aug 2008 13:52:00 -0000	[thread overview]
Message-ID: <994439.20087.qm@web37603.mail.mud.yahoo.com> (raw)

Hi Ho!

On Thu, 07/31/08, "Kastil" <lordgalloth@gmail.com> wrote:

> Hello,
> 
> Is there any description of all possible warning that gcc can produce? I  
> would like to found some document, when all warning would be described  
> instead of constantly searching through Internet.
> Thank for all suggestions

You may as well try to contact "Simon Toth" <happy.cerberus@gmail.com> because he said on gcc-thread.147973@gcc.gnu.org that he would like to build a database about all GCC warnings and errors.

> Jan
> 
> -- 

Best regards,
Eus


      

             reply	other threads:[~2008-08-02 13:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-02 13:52 Eus [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-07-31 11:12 Kastil
2008-07-31 11:31 ` Eljay Love-Jensen
2008-07-31 15:33   ` Kastil
2008-07-31 17:07     ` Brian Dessent

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=994439.20087.qm@web37603.mail.mud.yahoo.com \
    --to=eus@member.fsf.org \
    --cc=gcc-help@gcc.gnu.org \
    --cc=lordgalloth@gmail.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).