This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: -fno-exceptions and libgcc.a


> It is reasonable to either change the default for exception handling
> to off for C,

I don't understand why there is even any discussion of this.
The default for C *has* to -fno-exceptions, unless there is
*no* cost for code that does not use the exceptions.
Anything else is a public relations disaster in terms
of the perceived code quality of gcc.  This *must* be
fixed before egcs (or gcc 2.8) is released.

There should be a #pragma or __sttribute__ to specify that
"this code needs to be robost in the presence of exceptions."
This could be turned on for qsort (the canonical example of
possibly throwing exceptions through C code), but off for
the rest of the C library.  Similar for libgcc.

	--Per Bothner
Cygnus Solutions     bothner@cygnus.com     http://www.cygnus.com/~bothner


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]