search for: seh_handlerdata

Displaying 5 results from an estimated 5 matches for "seh_handlerdata".

2011 May 19
0
[LLVMdev] MCSection and Win64 Exception Handling
...39;ve been watching llvm-commits, I've been working on Win64 exception handling support in LLVM. Unfortunately, I've hit a bit of a snag. I recently learned that GAS implemented its own set of Win64 EH directives. I've made ours compatible with GAS, but one problem remains. GAS's .seh_handlerdata directive is used to declare data that belongs in the language-specific handler's data area. The way it works in GAS is that it creates a pseudo-section containing the data that is later written to the unwind info structure. For LLVM, I suspect I have to do something similar. Trouble is, MCSect...
2018 Feb 06
3
What does a dead register mean?
Hi, My understanding of a "dead" register is a def that is never used. However, when I dump the MI after reg alloc on a simple program I see the following sequence: ADJCALLSTACKDOWN64 0, 0, 0, *implicit-def dead %rsp*, implicit-def dead %eflags, implicit-def dead %ssp, implicit %rsp, implicit %ssp CALL64pcrel32 @foo, <regmask %bh %bl %bp %bpl %bx %ebp %ebx %rbp %rbx %r12 %r13 %r14
2017 Nov 21
2
question about xray tls data initialization
...eax, dword ptr [rsp + 4] add eax, 1 mov dword ptr [rsp + 4], eax jmp .LBB0_1 .LBB0_4: # %for.end mov eax, dword ptr [rsp + 8] add rsp, 16 .p2align 1, 0x90 .Lxray_sled_1: ret nop word ptr cs:[rax + rax + 512] .seh_handlerdata .text .seh_endproc # -- End function .section xray_instr_map,"y" .Lxray_sleds_start0: .quad .Lxray_sled_0 .quad call .byte 0x00 .byte 0x00 .byte 0x00 .zero 13 .quad .Lxray_sled_1 .q...
2011 May 20
1
[LLVMdev] LLVMdev Digest, Vol 83, Issue 33
...I've been working on > Win64 exception handling support in LLVM. Unfortunately, I've hit a bit > of a snag. > > I recently learned that GAS implemented its own set of Win64 EH > directives. I've made ours compatible with GAS, but one problem remains. > > GAS's .seh_handlerdata directive is used to declare data that belongs in > the language-specific handler's data area. The way it works in GAS is > that it creates a pseudo-section containing the data that is later > written to the unwind info structure. For LLVM, I suspect I have to do > something similar...
2017 Nov 16
2
question about xray tls data initialization
I'm learning the xray library and try if it can be built on windows, in xray_fdr_logging_impl.h line 152 , comment written as // Using pthread_once(...) to initialize the thread-local data structures but at line 175, 183, code written as thread_local pthread_key_t key; // Ensure that we only actually ever do the pthread initialization once. thread_local bool UNUSED Unused = [] {