search for: eh_func_beginxx

...(ISA-encoded meaning this one bit in the case of mips16 ISA). > > I'm planning to add a virtual method called EmitDebugLabel to MCStreamer > which just calls method EmitLabel. > > Because of some luck, for exception handling at least, I really only > need to EmitDebugLabel for eh_func_beginXX. > > The other entries in the exception table are all a-b, except for > eh_func_beginXX, the 1 bits will cancel each other out. I don't know if > this is sufficient for actual dwarf info for debugging; i have not > thought through this yet. > > The real solution that gcc us...

...er vs ISA-encoded address (ISA-encoded meaning this one bit in the case of mips16 ISA). I'm planning to add a virtual method called EmitDebugLabel to MCStreamer which just calls method EmitLabel. Because of some luck, for exception handling at least, I really only need to EmitDebugLabel for eh_func_beginXX. The other entries in the exception table are all a-b, except for eh_func_beginXX, the 1 bits will cancel each other out. I don't know if this is sufficient for actual dwarf info for debugging; i have not thought through this yet. The real solution that gcc uses is to distinguish these two...

mips16 has some unusual requirements for label symbols in .s. I think that arm thumb has the same issue but have not located yet how this is handled. When you have a label of an instruction in mips16, when you reference the label, the linker adds a 1 to the address. When you call an odd numbered address, the procesor switches to mips16 mode and when you call an even numbered address it