Displaying 6 results from an estimated 6 matches for "endscope".
2010 Aug 24
0
[LLVMdev] help converting llvm metadata into dwarf tags
...d the tag definitions in include/llvm/Support/Dwarf.h and added my
> own.
> lib/CodeGen/AsmPrinter/DwarfDebug.cpp seems to be the only place that emits
> dwarf data into the assembly stream.
>
See have DwarfDebug.cpp handles DebugLoc attached with each instruction
(::beginScope() and ::endScope()).
> It also seems to create a DebugInfoFinder which accesses the IR
> instructions.
>
This path will allow you to browse entire function and collect info which
you can use later on.
-
Devang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://li...
2019 Nov 06
9
FileCheck idiom difficulties
Hi all,
Many of our lit tests use FileCheck and a tool like llvm-readobj to check
properties of a section header/symbol/etc. A typical (pseudoised for
brevity) output to match against might be something like the following:
Symbols [
Symbol {
Name: foo
Value: 0
Type: Function
Section: .foo (1)
}
Symbol {
Name: bar
Value: 1
Type: Object
Section: .foo (1)
}
]
2010 Aug 23
2
[LLVMdev] help converting llvm metadata into dwarf tags
Dear all,
I'd like to find the memory location of certain instructions in a
compiled/linked binary. During the IR phase, I tag instructions I'm
interested in with LLVM'-2.7's new metadata (MDNodes with an identifiable
ID). I'd now like to propagate that data to the assembly via a custom DWARF
tag I attach to each X86 instruction created from a tagged IR instruction.
This will
2010 Sep 07
1
[LLVMdev] help converting llvm metadata into dwarf tags
...de/llvm/Support/Dwarf.h and added
>> my own.
>> lib/CodeGen/AsmPrinter/DwarfDebug.cpp seems to be the only place that
>> emits dwarf data into the assembly stream.
>>
>
> See have DwarfDebug.cpp handles DebugLoc attached with each instruction
> (::beginScope() and ::endScope()).
>
>
>> It also seems to create a DebugInfoFinder which accesses the IR
>> instructions.
>>
>
> This path will allow you to browse entire function and collect info which
> you can use later on.
>
> -
> Devang
>
-------------- next part --------------...
2018 Mar 14
0
LLVM opt unable to vectorize PolyBench code
It would help if you sent the IR you're giving to opt or at least a
complete C function and your clang command line.
~Craig
On Wed, Mar 14, 2018 at 3:05 PM, hameeza ahmed <hahmed2305 at gmail.com> wrote:
> Hello,
>
> I m unable to vectorize following kernel by opt tool;
>
> for (i = 0; i < _PB_NI; i++)
> for (j = 0; j < _PB_NJ; j++)
> {
>
2018 Mar 14
2
LLVM opt unable to vectorize PolyBench code
Hello,
I m unable to vectorize following kernel by opt tool;
for (i = 0; i < _PB_NI; i++)
for (j = 0; j < _PB_NJ; j++)
{
tmp[i][j] = 0;
for (k = 0; k < _PB_NK; ++k)
tmp[i][j] += alpha * A[i][k] * B[k][j];
}
for (i = 0; i < _PB_NI; i++)
for (j = 0; j < _PB_NL; j++)
{
D[i][j] *= beta;
for (k = 0; k < _PB_NJ; ++k)
D[i][j] +=