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: two libgcc.so thoughts


    Where do you plan to put the EH bits?  Those should ideally be common
    between Java, C++, Python, C#, ADA and all the other languages that do
    this kind of stuff.  The IA64 EH model makes it easier to get this
    right, but what do you plan to do with the DWARF stuff?

I think they should go into libgcc.

My criteria would be that if calls to the functions occur in
the core compiler, the functions ought to be in libgcc.

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