public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/31983] Add option to gcc to display specific language manual section reference for error/warning encountered.
Date: Tue, 10 May 2011 10:05:00 -0000	[thread overview]
Message-ID: <bug-31983-4-9eY4VSZ1lT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-31983-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31983

Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |manu at gcc dot gnu.org

--- Comment #13 from Manuel López-Ibáñez <manu at gcc dot gnu.org> 2011-05-10 09:57:55 UTC ---
I have come around on this issue (and the color output). I now think it would
be useful to have an extra verbose mode. It is clear it won't be implemented by
existing GCC devs and probably it won't be accepted in mainline GCC, so it will
have to be a plugin. 

The first step is to have a significant number of verbose descriptions. I have
started a list but it needs a lot more contributions:

http://gcc.gnu.org/wiki/VerboseDiagnostics

The second step would be to enable plugins to intercept warning/error messages
and add their own actions (in this case, just printing the verbose output).
Even if nobody bothers to finish this second step, the list itself would be
helpful.


       reply	other threads:[~2011-05-10 10:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-31983-4@http.gcc.gnu.org/bugzilla/>
2011-05-10 10:05 ` manu at gcc dot gnu.org [this message]
2007-05-18  0:03 [Bug c/31983] New: " jamesodhunt at gmail dot com
2007-05-18  0:13 ` [Bug c/31983] " pinskia at gcc dot gnu dot org
2007-05-18  2:27 ` fang at csl dot cornell dot edu
2007-05-18 13:17 ` manu at gcc dot gnu dot org
2007-05-21  1:52 ` pinskia at gcc dot gnu dot org
2008-05-06 18:00 ` esigra at gmail dot com
2008-05-06 18:22 ` pinskia at gcc dot gnu dot org
2008-05-06 18:48 ` esigra at gmail dot com
2008-05-07 10:07 ` manu at gcc dot gnu dot org
2008-05-07 13:09 ` esigra at gmail dot com
2008-05-08 10:45 ` manu at gcc dot gnu dot org
2008-09-03  2:44 ` pinskia at gcc dot gnu dot org
2008-09-21 20:39 ` esigra at gmail dot com
2008-12-24 23:16 ` pinskia at gcc dot gnu dot 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-31983-4-9eY4VSZ1lT@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).