search for: needsunwindtableentry

I'm cross compiling using clang for x86_64 windows using SEH exceptions. If at all possible, I would like to enable unwind tables to be generated in debug_frame, but I was unable to figure out how to accomplish this. Is there a supported way? Thanks, Keno

...t. Despite this we should still emit the unwind entry for the EXIDX_CANTUNWIND value, which is always done. Another issue is that canThrow (!NoUnwind) is set by default. Setting NoUnwind is an optimisation which is not handled by the ARM Streamer. A first approach was to have the backend return needsUnwindTableEntry() false if noexception support, but unwind tables can be used without exception handler (e.g) for debug infos or C unwind with attribute cleanup, and this happened to be quite intrusive... But simpler, when the exceptions are not enabled, we should be able to remove them. Just passing this thi...

I'd love to hear more details. Are you saying that this infinite loop is a limitation of EHABI table format, and not something that can be fixed in the compiler? Meanwhile, please notice that gcc behavior matches current clang behavior that I described above. We would not want to create an incompatibility. On Fri, Feb 14, 2014 at 8:42 PM, Logan Chien <tzuhsiang.chien at gmail.com>

...out whether we can apply this optimization when the caller function has the uwtable attribute and requires the unwind table. # Unwind Table and Can't Unwind The mixture of uwtable and nounwind will cause another problem. IMO, it is incorrect to decide whether to emit [can't unwind] with !needsUnwindTableEntry() [2]. The needsUnwindTableEntry() is defined as either the function has uwtable attribute or the function does not have nounwind. Thus, !needsUnwindTableEntry() imples not having uwtable attribute and having nounwind. As the result, the [can't unwind] won't be generated for the following f...

...rfCFI)*/*/ /**/ break;/*/ // for (auto &F: M.getFunctionList()) {// // // If the module contains any function with unwind data,// // // .eh_frame has to be emitted.// // // Ignore functions that won't get emitted.// // if (!F.isDeclarationForLinker() && F.needsUnwindTableEntry()) {// //*isCFIMoveForDebugging = false;*// // break;// // }// / The ExceptionHandlingType for AArch64 is ExceptionHandling::DwarfCFI whereas for ARM it is ExceptionHandling::ARM. As a result, the behavior of the .cfi_sections differs for ARM vs AArch64. Due to this, my test which c...