search for: myarch_regs

...r values from the in-memory structure based on the DWARF number. This is usually quite small because the easiest way of dumping the registers is to store each register set contiguously in memory in the same order that as their DWARF numbers, so you end up with a struct something like this: struct MyArch_Regs { int64_t GPRs[32]; }; And the get function is just doing GPRs[RegNo - MyArch_GPR0]. LLVM’s libUnwind has a very clean structure. Adding MIPS support took a couple of hours. All of the unwinder support is generic other than the mapping from DWARF register numbers to some concrete mechanism for...

...tructure > based on the DWARF number. This is usually quite small because the easiest > way of dumping the registers is to store each register set contiguously in > memory in the same order that as their DWARF numbers, so you end up with a > struct something like this: > > struct MyArch_Regs > { > int64_t GPRs[32]; > }; > > And the get function is just doing GPRs[RegNo - MyArch_GPR0]. > > LLVM’s libUnwind has a very clean structure. Adding MIPS support took a > couple of hours. All of the unwinder support is generic other than the > mapping from DWA...

On 15 January 2018 at 12:49, 陳韋任 via llvm-dev <llvm-dev at lists.llvm.org> wrote: > - CFI directives: > > This is for .eh_frame section. Basically all the targets insert CFI > directives in FrameLowering, but I am not sure exactly when/where I should > do so. The directives are there to describe where the unwinder should look to find out what each register's value

Hi All, I would like to know in order to support exception handling for particular target, what need to be done. After doing some investigation, I can think of the following items with questions: - CFI directives: This is for .eh_frame section. Basically all the targets insert CFI directives in FrameLowering, but I am not sure exactly when/where I should do so. -