--- Comment #11 from reichelt at gcc dot gnu dot org 2006-03-22 20:14
---
Fixed in mainline.
I.e. the C and C++ frontend now return "4" if an ICE occurred,
and a code less than 4 if a regular error occurred.
(The Fortran frontend has been doing this already.)
In order to see the exit
--- Comment #10 from reichelt at gcc dot gnu dot org 2006-03-22 19:36
---
Subject: Bug 22600
Author: reichelt
Date: Wed Mar 22 19:36:22 2006
New Revision: 112292
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=112292
Log:
PR driver/22600
* system.h (ICE_EXIT_COD
--- Comment #9 from patchapp at dberlin dot org 2006-03-19 21:03 ---
Subject: Bug number PR 22600
A patch for this bug has been added to the patch tracker.
The mailing list url for the patch is
http://gcc.gnu.org/ml/gcc-patches/2006-03/msg01203.html
--
http://gcc.gnu.org/bugzilla/s
--- Additional Comments From mmitchel at gcc dot gnu dot org 2005-09-08
03:07 ---
I think this is a good idea. I don't think we need a switch; this should just
be the default. We also need a documentation update to mention this. And, I
think the default ICE_EXIT_CODE shold be "2", unl
--- Additional Comments From flash at pobox dot com 2005-07-23 05:10
---
Thanks very much, patch 9330 works well (though I had to apply the second
change in gcc.c manually,
since someone changed commands[i].prog to commands[j].prog later than my copy
of the 4.0.1 sources).
I've adde
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-07-22
16:48 ---
(In reply to comment #5)
I should mention that we do print out the line/file which an assert fails
inside gcc.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22600
--- Additional Comments From flash at pobox dot com 2005-07-22 16:04
---
Looking for a string pattern in the output leaves you vulnerable to
correctly-rejected files which
happen to generate that pattern in an error message. That's probably less of
an issue with GCC's hand-
craft
--- Additional Comments From reichelt at gcc dot gnu dot org 2005-07-22
14:36 ---
We really do want this.
See the thread in http://gcc.gnu.org/ml/gcc/2005-02/msg00953.html
--
What|Removed |Added
---
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-07-21
22:14 ---
One more thing usually ICEs have better error messages than just Segmentation
fault.
some give the line number in GCC's source where it occurred.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22600
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-07-21
22:12 ---
I don't see why it should be different than 1. It would only be helpful when
you have automated builds
but even then you need to look at the errors.
and for recursive crash testing you need to look for a
10 matches
Mail list logo
