AVR Freaks

I guess I should have been more clear:

My goal would be to fill in the missing platform-specific pieces to allow normal c++ try/throw/catch blocks to compile and link under avr-g++, so that my cross-platform class libraries can assume correct (and ideally, but not necessarily, relatively fast-performing) behaviour on the AVR target.

I specifically DO NOT care about std::exception objects; they would almost certainly pull in heap dependencies which I am not interested in.

It is absolutely easy to use the heap. I even have the stubs functions in place to make the C++ new and delete operators work correctly -- if I wanted to do so.

But I explicitly don't want to do it.

(edit: Ironically, my version of the C++ new operator explicitly violates the relevant standards because of the very issue I am raising right now: I cannot throw a std::bad_alloc because try/throw/catch is unimplemented. I am fine with that deviation because, as I keep on saying, up until now I have not actually used the heap at all, so the violation quite simply cannot come back to bite me.)

And, until proven otherwise, quite frankly it's irrelevant to the central thrust of my question.

(edit: Based on a follow-up answer, it is possible -- depending on GCC internals -- that the compiler's internal expectations about exceptions might inextricably make the heap a mandatory part of the throwing process. But without that extra GCC insider knowledge, I still cannot actually answer that.)