Displaying 6 results from an estimated 6 matches for "dw_lang_c89".
Did you mean:
dw_lang_c
2017 Mar 11
2
What does it mean by a "DICompileUnit missing from llvm.dgs.cu" ? | Where is the error ?
Hello,
One of my Julia programs failed to execute with the following error,
DICompileUnit not listed in llvm.dbg.cu
!11 = distinct !DICompileUnit(language: DW_LANG_C89, file: !3, producer:
"julia", isOptimized: true, runtimeVersion: 0,emissionKind: FullDebug, enums
: !12)
This was generated by verifyModule(*GPUModule,&(llvm::errs())From whithin
PPCGCodeGeneration.cpp in Polly.
>From <llvm_src>/test/Verifier/dbg-orphaned-compileunit.ll, I...
2016 Jul 26
4
'invalid subroutine type ref' when linking custom metadata
...s? Thanks,
Robin
> cat a.ll
define void @a() {
ret void
}
!bar = !{!3}
!3 = !{void ()* @a}
> cat b.ll
define void @foo() !dbg !20 {
ret void
}
!llvm.module.flags = !{!17, !18}
!0 = distinct !DICompileUnit(language: DW_LANG_C89, file: !1)
!1 = !DIFile(filename: "x.c", directory: "/tmp")
!17 = !{i32 2, !"Dwarf Version", i32 4}
!18 = !{i32 2, !"Debug Info Version", i32 3}
!20 = distinct !DISubprogram(name: "foo", scope: !1, file: !1, line: 92, type: !21, unit...
2017 Mar 12
2
What does it mean by a "DICompileUnit missing from llvm.dgs.cu" ? | Where is the error ?
...SRIVALLABH SINGAPURAM via llvm-dev
> <
> llvm-dev at lists.llvm.org> wrote:
>
> > Hello,
> >
> > One of my Julia programs failed to execute with the following error,
> > DICompileUnit not listed in llvm.dbg.cu
> > !11 = distinct !DICompileUnit(language: DW_LANG_C89, file: !3, producer:
> > "julia", isOptimized: true, runtimeVersion: 0,emissionKind: FullDebug,
> > enums: !12)
> >
> > This was generated by verifyModule(*GPUModule,&(llvm::errs())From whithin
> > PPCGCodeGeneration.cpp in Polly.
> >
> > From...
2014 Jun 02
2
[LLVMdev] [lldb-dev] MCJIT Mach-O JIT debugging
...ocated correctly (I think):
>
> 0x00000000: Compile Unit: length = 0x00000045 version = 0x0003 abbr_offset = 0x00000000 addr_size = 0x08 (next CU at 0x00000049)
>
> 0x0000000b: TAG_compile_unit [1] *
> AT_producer( "julia" )
> AT_language( DW_LANG_C89 )
> AT_name( "string.jl" )
> AT_stmt_list( 0x00000000 )
> AT_comp_dir( "." )
> AT_APPLE_optimized( 0x01 )
> AT_low_pc( 0x0000000112f5f1c0 )
> AT_high_pc( 0x000006fb )
>
> 0x000...
2016 Jul 27
1
'invalid subroutine type ref' when linking custom metadata
...}
>>
>> !bar = !{!3}
>>
>> !3 = !{void ()* @a}
>>
>>> cat b.ll
>> define void @foo() !dbg !20 {
>> ret void
>> }
>>
>> !llvm.module.flags = !{!17, !18}
>>
>> !0 = distinct !DICompileUnit(language: DW_LANG_C89, file: !1)
>> !1 = !DIFile(filename: "x.c", directory: "/tmp")
>> !17 = !{i32 2, !"Dwarf Version", i32 4}
>> !18 = !{i32 2, !"Debug Info Version", i32 3}
>> !20 = distinct !DISubprogram(name: "foo", scope: !1, file: !...
2014 Jun 02
2
[LLVMdev] [lldb-dev] MCJIT Mach-O JIT debugging
I didn't get to work on this more last week, but I'll look at incorporating
that suggestion.
The other question of course is how to do this in LLDB. Right, now what I'm
doing is going through and adjusting the load address of every leaf in the
section tree. That basically works and gets me backtraces with the correct
function names and the ability to set breakpoints at functions in