public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/32614]  New: -fmessage-length documentation and implementation disagree
@ 2007-07-03 18:06 tromey at gcc dot gnu dot org
  2010-02-21  0:31 ` [Bug c++/32614] " manu at gcc dot gnu dot org
  2010-02-21  0:46 ` manu at gcc dot gnu dot org
  0 siblings, 2 replies; 3+ messages in thread
From: tromey at gcc dot gnu dot org @ 2007-07-03 18:06 UTC (permalink / raw)
  To: gcc-bugs

doc/invoke.texi says:

Try to format error messages so that they fit on lines of about @var{n}
characters.  The default is 72 characters for @command{g++} and 0 for the rest
of
the front ends supported by GCC@.

However, cp/cxx-pretty-print.c seems to set the default to 0:

  pp_set_line_maximum_length (pp, 0);

See this thread:

http://gcc.gnu.org/ml/gcc-patches/2007-03/msg01948.html

There is some disagreement as to whether this is a documentation bug
or a code bug.


-- 
           Summary: -fmessage-length documentation and implementation
                    disagree
           Product: gcc
           Version: 4.3.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: tromey at gcc dot gnu dot org


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


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug c++/32614] -fmessage-length documentation and implementation disagree
  2007-07-03 18:06 [Bug c++/32614] New: -fmessage-length documentation and implementation disagree tromey at gcc dot gnu dot org
@ 2010-02-21  0:31 ` manu at gcc dot gnu dot org
  2010-02-21  0:46 ` manu at gcc dot gnu dot org
  1 sibling, 0 replies; 3+ messages in thread
From: manu at gcc dot gnu dot org @ 2010-02-21  0:31 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #1 from manu at gcc dot gnu dot org  2010-02-21 00:31 -------
*** Bug 32587 has been marked as a duplicate of this bug. ***


-- 

manu at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fritz at intrinsity dot com


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


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug c++/32614] -fmessage-length documentation and implementation disagree
  2007-07-03 18:06 [Bug c++/32614] New: -fmessage-length documentation and implementation disagree tromey at gcc dot gnu dot org
  2010-02-21  0:31 ` [Bug c++/32614] " manu at gcc dot gnu dot org
@ 2010-02-21  0:46 ` manu at gcc dot gnu dot org
  1 sibling, 0 replies; 3+ messages in thread
From: manu at gcc dot gnu dot org @ 2010-02-21  0:46 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #2 from manu at gcc dot gnu dot org  2010-02-21 00:46 -------
    Tom,

    this is not a code bug. Perhaps is the wrong default. So please, unless you
want to change the current default, commit your doc patch and let someone
interested in changing the default to get a patch approved for that.


-- 

manu at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2010-02-21 00:46:30
               date|                            |


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


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2010-02-21  0:46 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-07-03 18:06 [Bug c++/32614] New: -fmessage-length documentation and implementation disagree tromey at gcc dot gnu dot org
2010-02-21  0:31 ` [Bug c++/32614] " manu at gcc dot gnu dot org
2010-02-21  0:46 ` manu at gcc dot gnu dot org

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).