Re: -fno-exceptions and libgcc.a

[Oleg Krivosheev <kriol at fnal dot gov>]

hi,

On Sat, 4 Oct 1997, Per Bothner wrote:

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

hmm...
It will expose g++ specific EH in the libc. What Linux people
with KAI C++ or Comeau C++ supposed to do if glibc
will be compiled with g++ exceptions? looks like
linker modifications a la Mark Mitchel is required.

Well, published Linux C++ ABI will be the best solution IMHO.

regards

OK