search for: progbits

Martin Richtarsky <s at martinien.de> writes: > Rafael Avila de Espindola wrote: >>> I will retry with clang trunk, when it reproduces I will build some >>> other >>> large project (that has DSOs) using our compile/link options (they are >>> not >>> that special, I think). >> >> If you can try lld trunk too that would be awesome.

...== void ex_func(int, int, int); ======================================================================== Asm -O0 ======================================================================== .file "a.c" .file 1 "/home/marco/clang_issue/a.c" .section .debug_info,"", at progbits .Lsection_info: .section .debug_abbrev,"", at progbits .Lsection_abbrev: .section .debug_aranges,"", at progbits .section .debug_macinfo,"", at progbits .section .debug_line,"", at progbits .Lsection_line: .section .debug_loc,"", at progbits ....

.../ C > int > main(int argc, char *argv[]) > { > int a = 11; > int b = 22; > int c = a+b; > return c; > } > > ###################################### > # asm including dwarf debugging info > .file "test.c" > .section .debug_info,"", at progbits > Lsection_info: > .section .debug_abbrev,"", at progbits > Lsection_abbrev: > .section .debug_aranges,"", at progbits > .section .debug_macinfo,"", at progbits > .section .debug_line,"", at progbits > Lsection_line: > .section .debug...

Hello, Building an object file with ToT Clang: > Debug+Asserts/bin/clang -o penalty2.o -c penalty.cpp -g These are the debug-related sections produced: $ readelf -S penalty2.o |grep debug [ 5] .debug_info PROGBITS 0000000000000000 00000bd0 [ 6] .rela.debug_info RELA 0000000000000000 00002f80 [ 7] .debug_abbrev PROGBITS 0000000000000000 000010b8 [ 8] .debug_aranges PROGBITS 0000000000000000 000011c3 [ 9] .debug_macinfo PROGBITS 000000000000000...

On Fri, Apr 19, 2013 at 09:47:28AM -0700, reed kotler wrote: > The clean solution is probably to add two additional function > attributes to cover these additional pieces, namely "ax" and > @progbits. Extend the section attribute to allow additional parameters? Joerg

All of this information is contained in the DWARF debug info that you must generate. Are you generating DWARF? If not, you will need to. If so, please attach an example program that contains DWARF and specify which function you are having trouble getting variable information for. Greg Clayton On Feb 18, 2014, at 12:44 AM, 杨勇勇 <triple.yang at gmail.com> wrote: > Hi, all > > I

On 04/19/2013 12:43 PM, Joerg Sonnenberger wrote: > On Fri, Apr 19, 2013 at 09:47:28AM -0700, reed kotler wrote: >> The clean solution is probably to add two additional function >> attributes to cover these additional pieces, namely "ax" and >> @progbits. > > Extend the section attribute to allow additional parameters? > > Joerg > The idea would be to create additional function attributes. I have not spent time thinking this through yet. section_flags("flags") section_type("type") others.... so then void x(int...

Hi, all I ported llvm backend and lldb recently. Both tools can basically work. lldb is able to debug programs in asm style and frame unwinding is OK. But "frame variable XX" does not work because lldb is not able to determine the address of XX from debug info. Can someone give any clue? Thanks in advance. -- 杨勇勇 (Yang Yong-Yong) -------------- next part -------------- An HTML

...ldr from constant pool ldr r0, =0x103 3. Duplicate constants should be merged to the same constant pool location ldr r0, =0x103 ... ldr r0, =0x103 4. A section defined in multiple pieces is merged and uses a single constant pool For example, .section e, "ax", %progbits f6: ldr r0, =0x103 .section f, "ax", %progbits f7: add r0, r0, r0 .section e, "ax", %progbits f8: add r0, r0, r0 ldr r0, =0x105 should only produce one constant pool for section e. 5. Check that symbols can be loaded using...

...ps 16(%rdi), %xmm1 addps (%rsi), %xmm0 addps 16(%rsi), %xmm1 movaps %xmm1, 16(%rdi) movaps %xmm0, (%rdi) ret .Ltmp0: .size _fun1, .Ltmp0-_fun1 .cfi_endproc .section ".note.GNU-stack","", at progbits $ llc -o - -mattr avx avx.ll .file "avx.ll" .text .globl _fun1 .align 16, 0x90 .type _fun1, at function _fun1: # @_fun1 .cfi_startproc # BB#0: # %_L1 pu...

...el4: .Llabel1: callq g .Llabel2: # BB#1: # %c addq $8, %rsp ret .LBB1_2: # %u .Llabel3: addq $8, %rsp ret .size f, .-f .Leh_func_end1: .section .gcc_except_table,"a", at progbits .align 4 GCC_except_table1: .byte 0 # Padding .byte 0 # Padding .Lexception1: .byte 255 # @LPStart format (omit...

...movl $.L__string_27, %edi xorb %al, %al call printf xorl %eax, %eax addq $56, %rsp ret .size _ZN4N0014Main5test5EN2IO6WriterEiA_l, .-_ZN4N0014Main5test5EN2IO6WriterEiA_l .Lfunc_end153: .Leh_func_end153: .section .gcc_except_table,"a", at progbits .align 4 GCC_except_table153: .byte 0x0 # Padding .Lexception153: .byte 0xFF # @LPStart format (DW_EH_PE_omit) .byte 0x0 # @TType format (DW_EH_PE_abspt...

...g++ to preprocess and compile my application stopping it (-S) before the assembler because I would like to use a different assembler (it comes from another processor model). It seems that the output assembly code is not compatible with the assembler but I´M not sure about that. The errors are with @progbits, weak and hidden sections. See below: " obj/main.o.s(1,63): ' .section .text.__ZNSt3__120__vector_base_commonILb1EEC1Ev,"axG", at progbits,__ZNSt3__120__vector_base_commonILb1EEC1Ev,comdat' obj/main.o.s(1,63): error: 'G", at progbits,__ZNSt3__120__vector_base_com...

...2:43 PM, Joerg Sonnenberger wrote: >> >> On Fri, Apr 19, 2013 at 09:47:28AM -0700, reed kotler wrote: >>> >>> The clean solution is probably to add two additional function >>> attributes to cover these additional pieces, namely "ax" and >>> @progbits. >> >> >> Extend the section attribute to allow additional parameters? >> >> Joerg >> > The idea would be to create additional function attributes. > I have not spent time thinking this through yet. > > section_flags("flags") > section_ty...

...quot;, "Testing vmovdqu %ymm2,(%ecx)..."); + if ( stack_exec && cpu_has_avx ) + { + extern const unsigned char vmovdqu_to_mem[]; + + asm volatile ( "vpcmpeqb %%xmm2, %%xmm2, %%xmm2\n" + ".pushsection .test, \"a\", @progbits\n" + "vmovdqu_to_mem: vmovdqu %%ymm2, (%0)\n" + ".popsection" :: "c" (NULL) ); + + memcpy(instr, vmovdqu_to_mem, 15); + memset(res, 0x55, 128); + memset(res + 16, 0xff, 16); + memset(res + 20,...

...section allocated for the stack which roughly looks like the following. .stack : { . += __stack_size__; } > ram Using the linker in the gcc arm toolchain, arm-none-eabi-ld, this section is automatically set to type NOBITS, however, when linking with version 10.0.0 of ld.lld, the section type is PROGBITS. Here is the output when using readelf. *ld.lld* Section Headers: [Nr] Name Type Addr Off Size ES Flg Lk Inf Al ... [ 5] .stack PROGBITS 1ffff000 0014f0 000400 00 A 0 0 1 *arm-none-eabi-ld* Section Headers: [Nr] Name Type...

...p, i32 1, i32 0 ret i32 %ret } And I expected that minimal positive denormalized double times -0.5 is equal to -0.0, so correct exit code is 1. llvm-3.4.2 on x86 linux target produced the following assembly: .file "fpfail.ll" .section .rodata.cst8,"aM", at progbits,8 .align 8 .LCPI0_0: .quad -4620693217682128896 # double -0.5 .LCPI0_1: .quad -9223372036854775808 # double -0 .text .globl main .align 16, 0x90 .type main, at function main: # @main .c...

...0x103 > 3. Duplicate constants should be merged to the same constant pool location > ldr r0, =0x103 > ... > ldr r0, =0x103 > 4. A section defined in multiple pieces is merged and uses a single constant > pool > For example, > > .section e, "ax", %progbits > f6: > ldr r0, =0x103 > .section f, "ax", %progbits > f7: add r0, r0, r0 > .section e, "ax", %progbits > f8: > add r0, r0, r0 > ldr r0, =0x105 > > should only produce one constant pool for section e. &g...

This came about in trying to implement some stubs used by gcc mips16 for allowing floating point interoperability with mips32. You get the following looking code from gcc -mips16: # Stub function for foovf (float) .section .mips16.fn.foovf,"ax", at progbits .align 2 .set nomips16 .set nomicromips .ent __fn_stub_foovf .type __fn_stub_foovf, @function __fn_stub_foovf: la $25,foovf mfc1 $4,$f12 jr $25 .end __fn_stub_foovf .text $__fn_local_foovf = foovf Not being sure about the restriction of section to just "name", well docs can...

> It is exactly intended to handle section names as what they are -- > section names. The only reason it works with GCC is because it writes an > assembler stream. +1 Reed, this fails in gcc if you do LTO, no? > Joerg Cheers, Rafael