Projects

Fri May 5 13:49:00 GMT 2000

"Jonathan P. Olson" wrote:
> The exception handling patches are definitely alot messier than write
> barriers. Exceptions in gcc are currently quite broken on many architectures
> and terribly inefficient on others. There are two different exception handling
> strategies intermingled in the gcc code. Adding a third makes an enormous
> spaghetti bowl and is contrary to the overall goal of eliminating compilation
> options. I opted for just replacing the existing code, but I doubt if that's
> politically acceptable for gcc in general since libraries are currently built
> using the existing mechanism(s).

FYI I think one goal of GCC 3.0 is to eliminate the current sjlj
expection
handling mechanism. Apparently some maintainers feel it has caused more
trouble than it was worth.
-- 
Jeff Sturm
jeff.sturm@appnet.com