public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/37773] New: -Wfatal-errors aborts too early
@ 2008-10-08 16:18 carlo at gcc dot gnu dot org
2008-10-08 16:49 ` [Bug c++/37773] " carlo at gcc dot gnu dot org
` (2 more replies)
0 siblings, 3 replies; 8+ messages in thread
From: carlo at gcc dot gnu dot org @ 2008-10-08 16:18 UTC (permalink / raw)
To: gcc-bugs
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1511 bytes --]
Many errors span multiple lines. However, any of the first lines start with
'error:' (or so it seems) the rest is not printed anymore (with using
-Wfatal-errors).
For example:
hikaru:~/projects/cwchessboard/cwchessboard-objdir>make tstpgn
source='PgnDatabase.cc' object='tstpgn-PgnDatabase.o' libtool=no \
DEPDIR=.deps depmode=pch /bin/sh ../cwchessboard/depcomp \
g++ -DHAVE_CONFIG_H -I. -I../cwchessboard -DCWDEBUG
-I/usr/local/install/4.3.1/include $(pkg-config --cflags giomm-2.4) -g3
-Winline -Wfatal-errors -DDEBUG -c -o tstpgn-PgnDatabase.o `test -f
'PgnDatabase.cc' || echo '../cwchessboard/'`PgnDatabase.cc
../cwchessboard/MemoryBlockList.h: In member function âvoid
cwchess::pgn::DatabaseSeekable::read_async_open_ready(Glib::RefPtr<Gio::AsyncResult>&)â:
../cwchessboard/MemoryBlockList.h:124: error: âchar*
util::MemoryBlockNode::block_begin()â is private
compilation terminated due to -Wfatal-errors.
make: *** [tstpgn-PgnDatabase.o] Error 1
This is little useful. Now I have to recompile without -Wfatal-errors to find:
../cwchessboard/PgnDatabase.cc:52: error: within this context
--
Summary: -Wfatal-errors aborts too early
Product: gcc
Version: 4.3.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: carlo at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37773
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug c++/37773] -Wfatal-errors aborts too early
2008-10-08 16:18 [Bug c++/37773] New: -Wfatal-errors aborts too early carlo at gcc dot gnu dot org
@ 2008-10-08 16:49 ` carlo at gcc dot gnu dot org
2008-10-08 16:57 ` Andrew Thomas Pinski
2008-10-08 16:58 ` pinskia at gmail dot com
2008-10-08 20:02 ` rguenth at gcc dot gnu dot org
2 siblings, 1 reply; 8+ messages in thread
From: carlo at gcc dot gnu dot org @ 2008-10-08 16:49 UTC (permalink / raw)
To: gcc-bugs
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 482 bytes --]
------- Comment #1 from carlo at gcc dot gnu dot org 2008-10-08 16:48 -------
Here's another one:
../cwchessboard/PgnDatabase.cc:65: error: no matching function for call to
âutil::MemoryBlockList::append(gssize&)â
../cwchessboard/MemoryBlockList.h:232: note: candidates are: void
util::MemoryBlockList::append(Glib::RefPtr<util::MemoryBlockNode>&, size_t)
With -Wfatal-errors the second line is not printed.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37773
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Bug c++/37773] -Wfatal-errors aborts too early
2008-10-08 16:49 ` [Bug c++/37773] " carlo at gcc dot gnu dot org
@ 2008-10-08 16:57 ` Andrew Thomas Pinski
0 siblings, 0 replies; 8+ messages in thread
From: Andrew Thomas Pinski @ 2008-10-08 16:57 UTC (permalink / raw)
To: gcc-bugzilla; +Cc: gcc-bugs
Sent from my iPhone
On Oct 8, 2008, at 9:48 AM, "carlo at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org
> wrote:
>
>
> ------- Comment #1 from carlo at gcc dot gnu dot org 2008-10-08
> 16:48 -------
> Here's another one:
This expected behaviour of this option. It was not designed for users
really to use it. It was designed to make it easier and faster for
automatic reduction of ICEs.
Thanks,
Andrew Pinski
>
>
> ../cwchessboard/PgnDatabase.cc:65: error: no matching function for
> call to
> ‘util::MemoryBlockList::append(gssize&)’
> ../cwchessboard/MemoryBlockList.h:232: note: candidates are: void
> util::MemoryBlockList::append(Glib::RefPtr<util::MemoryBlockNode>&,
> size_t)
>
> With -Wfatal-errors the second line is not printed.
>
>
> --
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37773
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug c++/37773] -Wfatal-errors aborts too early
2008-10-08 16:18 [Bug c++/37773] New: -Wfatal-errors aborts too early carlo at gcc dot gnu dot org
2008-10-08 16:49 ` [Bug c++/37773] " carlo at gcc dot gnu dot org
@ 2008-10-08 16:58 ` pinskia at gmail dot com
2008-10-08 20:02 ` rguenth at gcc dot gnu dot org
2 siblings, 0 replies; 8+ messages in thread
From: pinskia at gmail dot com @ 2008-10-08 16:58 UTC (permalink / raw)
To: gcc-bugs
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1021 bytes --]
------- Comment #2 from pinskia at gmail dot com 2008-10-08 16:57 -------
Subject: Re: -Wfatal-errors aborts too early
Sent from my iPhone
On Oct 8, 2008, at 9:48 AM, "carlo at gcc dot gnu dot org"
<gcc-bugzilla@gcc.gnu.org
> wrote:
>
>
> ------- Comment #1 from carlo at gcc dot gnu dot org 2008-10-08
> 16:48 -------
> Here's another one:
This expected behaviour of this option. It was not designed for users
really to use it. It was designed to make it easier and faster for
automatic reduction of ICEs.
Thanks,
Andrew Pinski
>
>
> ../cwchessboard/PgnDatabase.cc:65: error: no matching function for
> call to
> âutil::MemoryBlockList::append(gssize&)â
> ../cwchessboard/MemoryBlockList.h:232: note: candidates are: void
> util::MemoryBlockList::append(Glib::RefPtr<util::MemoryBlockNode>&,
> size_t)
>
> With -Wfatal-errors the second line is not printed.
>
>
> --
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37773
>
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37773
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug c++/37773] -Wfatal-errors aborts too early
2008-10-08 16:18 [Bug c++/37773] New: -Wfatal-errors aborts too early carlo at gcc dot gnu dot org
2008-10-08 16:49 ` [Bug c++/37773] " carlo at gcc dot gnu dot org
2008-10-08 16:58 ` pinskia at gmail dot com
@ 2008-10-08 20:02 ` rguenth at gcc dot gnu dot org
2 siblings, 0 replies; 8+ messages in thread
From: rguenth at gcc dot gnu dot org @ 2008-10-08 20:02 UTC (permalink / raw)
To: gcc-bugs
------- Comment #3 from rguenth at gcc dot gnu dot org 2008-10-08 20:00 -------
Works as desigened. Really ;)
--
rguenth at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |INVALID
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37773
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug c++/37773] -Wfatal-errors aborts too early
[not found] <bug-37773-4@http.gcc.gnu.org/bugzilla/>
2011-01-24 23:19 ` pinskia at gcc dot gnu.org
2011-01-25 10:20 ` manu at gcc dot gnu.org
@ 2011-01-25 10:26 ` redi at gcc dot gnu.org
2 siblings, 0 replies; 8+ messages in thread
From: redi at gcc dot gnu.org @ 2011-01-25 10:26 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37773
--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> 2011-01-25 10:08:42 UTC ---
(In reply to comment #5)
> (In reply to comment #3)
> > Works as desigened. Really ;)
>
> So what is the point of -fmax-errors=N ?
Eh? Surely -fmax-errors *is* the option intended to be useful to users who want
to limit the error output.
Just because -Wfatal-errors is designed for something different, doesn't mean
-fmax-errors has no point.
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug c++/37773] -Wfatal-errors aborts too early
[not found] <bug-37773-4@http.gcc.gnu.org/bugzilla/>
2011-01-24 23:19 ` pinskia at gcc dot gnu.org
@ 2011-01-25 10:20 ` manu at gcc dot gnu.org
2011-01-25 10:26 ` redi at gcc dot gnu.org
2 siblings, 0 replies; 8+ messages in thread
From: manu at gcc dot gnu.org @ 2011-01-25 10:20 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37773
Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |manu at gcc dot gnu.org
--- Comment #5 from Manuel López-Ibáñez <manu at gcc dot gnu.org> 2011-01-25 09:57:03 UTC ---
(In reply to comment #3)
> Works as desigened. Really ;)
So what is the point of -fmax-errors=N ?
Shouldn't the documentation of Wfatal-errors say: "This option is not for users
but for compiler developers only"?
BTW, clang also supports -Wfatal-errors=option.
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug c++/37773] -Wfatal-errors aborts too early
[not found] <bug-37773-4@http.gcc.gnu.org/bugzilla/>
@ 2011-01-24 23:19 ` pinskia at gcc dot gnu.org
2011-01-25 10:20 ` manu at gcc dot gnu.org
2011-01-25 10:26 ` redi at gcc dot gnu.org
2 siblings, 0 replies; 8+ messages in thread
From: pinskia at gcc dot gnu.org @ 2011-01-24 23:19 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37773
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |navin.kumar at gmail dot
| |com
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> 2011-01-24 23:02:44 UTC ---
*** Bug 47429 has been marked as a duplicate of this bug. ***
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2011-01-25 10:09 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-10-08 16:18 [Bug c++/37773] New: -Wfatal-errors aborts too early carlo at gcc dot gnu dot org
2008-10-08 16:49 ` [Bug c++/37773] " carlo at gcc dot gnu dot org
2008-10-08 16:57 ` Andrew Thomas Pinski
2008-10-08 16:58 ` pinskia at gmail dot com
2008-10-08 20:02 ` rguenth at gcc dot gnu dot org
[not found] <bug-37773-4@http.gcc.gnu.org/bugzilla/>
2011-01-24 23:19 ` pinskia at gcc dot gnu.org
2011-01-25 10:20 ` manu at gcc dot gnu.org
2011-01-25 10:26 ` redi at gcc dot gnu.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).