Re: Soliciting help with libstdc++ and exceptions

["Martin v. Loewis" <martin at loewis dot home dot cs dot tu-berlin dot de>]

> Oh no!  You mean that whenever we add a new register to gcc, this is a
> binary incompatible change?!

Well, I leave that conclusion for the DWARF experts. At the moment, it
seems that we need to decouple frame_state from the internal register
numbering in gcc. It isn't that the architecture suddenly gets new
registers, is it? 

I see that flags and fpsr are new - do they really have to go into the
frame state? If so, are there additional 386 registers anticipated to
go into that structure?

> I think others suggested that libgcc.a needs to be made a shared
> library.  I'd suggest instead that it becomes part of glibc.

That would sound reasonable - if the structure wouldn't suddenly
change in size, when a new back-end is created. I understand that this
will rarely happen. What confuses me that it (addition of new hard
registers) happened at all.

Regards,
Martin