Displaying 20 results from an estimated 1000 matches similar to: "[LLVMdev] get function local debug info?"
2013 Nov 03
0
[LLVMdev] get function local debug info?
On Sat, Nov 2, 2013 at 4:17 PM, lu zhao <luzhao at cs.utah.edu> wrote:
> Hi,
>
> If I have an instance of DISubprogram, can I get the debug info of local
> variables of the function, including parameters?
>
> I tried to use the getVariables() function defined in DISubprogram, but it
> seemed to return an empty DIArray node when I ran my pass alone using opt.
> Do I
2013 Nov 03
0
[LLVMdev] get function local debug info?
+llvmdev because I accidentally dropped it
On Nov 3, 2013 6:57 AM, "David Blaikie" <dblaikie at gmail.com> wrote:
> You're welcome to provide a patch or I might get to it myself. Also this
> should be described in http://llvm.org/docs/SourceLevelDebugging.html if
> it isn't already
> On Nov 3, 2013 12:11 AM, "lu zhao" <luzhao at cs.utah.edu>
2011 Oct 28
3
[LLVMdev] DIBuilder - what's with the null compile units?
On Mon, Oct 24, 2011 at 9:17 AM, Devang Patel <dpatel at apple.com> wrote:
>
> On Oct 23, 2011, at 12:03 AM, Talin wrote:
>
> Just a follow up on this - I am still having problems, I never did figure
> out a solution. (I've been running with debug off for the last month so that
> I could get work done.)
>
> Here's what I am seeing: I am definitely calling
2011 Oct 28
0
[LLVMdev] DIBuilder - what's with the null compile units?
On Oct 27, 2011, at 10:39 PM, Talin wrote:
> On Mon, Oct 24, 2011 at 9:17 AM, Devang Patel <dpatel at apple.com> wrote:
>
> On Oct 23, 2011, at 12:03 AM, Talin wrote:
>
>> Just a follow up on this - I am still having problems, I never did figure out a solution. (I've been running with debug off for the last month so that I could get work done.)
>>
>>
2011 Oct 24
0
[LLVMdev] DIBuilder - what's with the null compile units?
On Oct 23, 2011, at 12:03 AM, Talin wrote:
> Just a follow up on this - I am still having problems, I never did figure out a solution. (I've been running with debug off for the last month so that I could get work done.)
>
> Here's what I am seeing: I am definitely calling DIBuilder::finalize(). I even put a debug print statement right after it, so that I could be sure that the
2013 Dec 04
2
[LLVMdev] DwarfDebug problems
Thanks for the quick response.
I wrote some code to search “llvm.dbg.cu” for the function (right before the failed assertion):
if (TheCU == nullptr) {
errs() << "compile unit: " << TheCU << "\n scopeNode(" << FnScope->getScopeNode() << ") => " << *FnScope->getScopeNode() << "\n";
auto fn =
2014 Jul 21
4
[LLVMdev] LTO type uniquing: ODR assertion failure
On Mon, Jul 21, 2014 at 3:48 PM, Manman Ren <manman.ren at gmail.com> wrote:
>
>
>
> On Mon, Jul 21, 2014 at 3:41 PM, David Blaikie <dblaikie at gmail.com> wrote:
>>
>> On Mon, Jul 21, 2014 at 3:35 PM, Manman Ren <manman.ren at gmail.com> wrote:
>> >
>> >
>> >
>> > On Mon, Jul 21, 2014 at 1:14 PM, David Blaikie
2014 Jul 21
2
[LLVMdev] LTO type uniquing: ODR assertion failure
On Mon, Jul 21, 2014 at 10:39 AM, Manman Ren <manman.ren at gmail.com> wrote:
>
>
>
> On Mon, Jul 14, 2014 at 11:32 AM, Manman Ren <manman.ren at gmail.com> wrote:
>>
>>
>> We still have access to types via MDNodes directly and the assertion that
>> assumes all accesses to DITypes are accessing the resolved DIType will fire
>>
>> i.e
2014 Jul 21
2
[LLVMdev] LTO type uniquing: ODR assertion failure
On Mon, Jul 21, 2014 at 3:35 PM, Manman Ren <manman.ren at gmail.com> wrote:
>
>
>
> On Mon, Jul 21, 2014 at 1:14 PM, David Blaikie <dblaikie at gmail.com> wrote:
>>
>> On Mon, Jul 21, 2014 at 10:39 AM, Manman Ren <manman.ren at gmail.com> wrote:
>> >
>> >
>> >
>> > On Mon, Jul 14, 2014 at 11:32 AM, Manman Ren
2013 Dec 04
2
[LLVMdev] DwarfDebug problems
In your transform I'd take a look at things like the individual basic
blocks you're replacing and the functions you're replacing and making
sure that the various lexical blocks are being changed at the same
time...
-eric
On Tue, Dec 3, 2013 at 11:12 PM, David Blaikie <dblaikie at gmail.com> wrote:
> On Tue, Dec 3, 2013 at 10:07 PM, Brandon Holt <bholt at
2011 Oct 23
2
[LLVMdev] DIBuilder - what's with the null compile units?
Just a follow up on this - I am still having problems, I never did figure
out a solution. (I've been running with debug off for the last month so that
I could get work done.)
Here's what I am seeing: I am definitely calling DIBuilder::finalize(). I
even put a debug print statement right after it, so that I could be sure
that the code was being executed. I also insured that it was getting
2014 Aug 27
6
[LLVMdev] Minimizing -gmlt
In an effort to fix inlined information for backtraces under DWARF Fission
in the absence of the split DWARF (.dwo) files, I'm planning on adding
-gmlt-like data to the .o file, alongside the skeleton CU.
Since that will involve teaching the LLVM about -gmlt (moreso than it
already has - the debug info LLVM metadata already describes -gmlt for the
purposes of omitting pubnames in that case) I
2013 Dec 04
0
[LLVMdev] DwarfDebug problems
On Tue, Dec 3, 2013 at 10:07 PM, Brandon Holt <bholt at cs.washington.edu> wrote:
> Thanks for the quick response.
>
> I wrote some code to search “llvm.dbg.cu” for the function (right before the
> failed assertion):
>
> if (TheCU == nullptr) {
> errs() << "compile unit: " << TheCU << "\n scopeNode(" <<
>
2013 Dec 04
0
[LLVMdev] DwarfDebug problems
How do I find and update the lexical blocks? Is, for example, “CloneFunction” doing this in a way I can copy?
I tried finding the subprogram node in “llvm.dbg.cu” and updating the function:
DISubprogram s(*subprog_iter);
if (s.getFunction() == F) {
s.replaceFunction(NF);
}
But this didn’t seem to have any effect. Do I need to do something similar with every basic block or something?
On Dec
2013 Dec 04
0
[LLVMdev] DwarfDebug problems
On Tue, Dec 3, 2013 at 9:04 PM, Brandon Holt <bholt at cs.washington.edu> wrote:
> In a pass I’m working on, I’ve done some manipulation of several functions, replacing them with new copies with different types, etc.
>
> The LLVM IR passes the verifier, but when I have debug symbols enabled (“-g”), I get the following error when Clang generates the Dwarf info (using a very recent
2013 Dec 04
2
[LLVMdev] DwarfDebug problems
In a pass I’m working on, I’ve done some manipulation of several functions, replacing them with new copies with different types, etc.
The LLVM IR passes the verifier, but when I have debug symbols enabled (“-g”), I get the following error when Clang generates the Dwarf info (using a very recent build of LLVM/Clang from Git mirror):
> Assertion failed: (TheCU && "Unable to find
2014 Jul 14
3
[LLVMdev] LTO type uniquing: ODR assertion failure
We still have access to types via MDNodes directly and the assertion that
assumes all accesses to DITypes are accessing the resolved DIType will fire
i.e assert(Ty == resolve(Ty.getRef()))
One example is the access to DIType via DIArray in SubroutineType. If all
elements in the type array are DITypes we can create a DITypeArray and use
that for SubroutineType's type array instead. But we
2017 Nov 22
3
Fw: modified mankendal
Hello DearI used modifiedmk package for trend analyses.this is my script
?require(modifiedmk)X1<-read.table("c:/elham/first article/r/Spring_NDVI-1.txt",skip=2,header=FALSE)d=dim(X1)
outMK<-matrix(-999,nrow=4,ncol=d[2])for (c in
2020 May 05
2
[Update][RFC] Refactor class hierarchy of VectorType in the IR
Nicolai,
My plan is to remove getNumElements() as soon as possible. Hopefully within the next few weeks. I just made a patch on my machine that marks it deprecated, and it generates a ton of warnings. Given that some build bots build with -Werror, I don't think we can mark it deprecated unless all the usages are first removed.
It occurs to me now that it might be good to mark it
2020 Apr 22
2
[Update][RFC] Refactor class hierarchy of VectorType in the IR
Hi,
I just wanted to give an update on the progress of this work. This morning I merged a patch to add the new vector types. I have added a FixedVectorType, as proposed below. I also added a ScalableVectorType. I found during my work that it is useful to be able to query isa<ScalableVectorType>(Ty). Additionally, I was concerned that it would become commonplace to take