search for: __typeid_typeid3_size

...class in that hierarchy. To avoid this, we only include resolutions in the summary and obtain the constants using absolute symbol references. Here is what the asm code may look like: baz: leaq __typeid_typeid3_global_addr(%rip), %rax subl %eax, %edi rorl $__typeid_typeid3_rotate_count, %edi cmpl $__typeid_typeid3_size, %edi ja .LBB2_1 movslq %edi, %rax leaq __typeid_typeid3_byte_array(%rip), %rcx movb (%rax,%rcx), %al andb $__typeid_typeid3_bitmask, %al shrb %al retq .LBB2_1: xorl %eax, %eax retq The appropriate representation for this at the IR level is the subject of the RFC entitled 'Absolute or "f...

..., we only > include resolutions in the summary and obtain the constants using absolute > symbol references. Here is what the asm code may look like: > > baz: > leaq __typeid_typeid3_global_addr(%rip), %rax > subl %eax, %edi > rorl $__typeid_typeid3_rotate_count, %edi > cmpl $__typeid_typeid3_size, %edi > ja .LBB2_1 > > movslq %edi, %rax > leaq __typeid_typeid3_byte_array(%rip), %rcx > movb (%rax,%rcx), %al > andb $__typeid_typeid3_bitmask, %al > shrb %al > retq > .LBB2_1: > xorl %eax, %eax > retq > > The appropriate representation for this at the IR le...