search for: slarin

...this is moving from llvm-commits to llvm-dev. On Feb 10, 2012, at 12:14 PM, Sergei Larin <slarin at codeaurora.org> wrote: > 1) Can a BB presented to the MI scheduler be _not_ terminated (end on a non > terminator MI) under any circumstances? Below you are speaking about "Empty > blocks, or blocks with only a single instruction that not a terminator..." - > What about...

On 04/26/2013 04:20 PM, Owen Anderson wrote: > > On Apr 26, 2013, at 3:07 PM, Sergei Larin <slarin at codeaurora.org > <mailto:slarin at codeaurora.org>> wrote: > >> Dan, >> Thank you for the quick and throughout reply. First paragraph pretty >> much sums it up. Unless there is more will to guaranty (or provide >> under flag) stricter version of IEEE adhere...

On Apr 26, 2013, at 3:07 PM, Sergei Larin <slarin at codeaurora.org> wrote: > > Dan, > > Thank you for the quick and throughout reply. First paragraph pretty much sums it up. Unless there is more will to guaranty (or provide under flag) stricter version of IEEE adherence, I doubt much can be done. > > So all of you...

On Aug 9, 2012, at 10:09 AM, Sergei Larin <slarin at codeaurora.org> wrote: > Yang, > > This might not be such a tough choice on engineering side - one of the > LLVM differentiators is the ground-up, early introduced support for VLIW > specific features… Actually, LLVM lacked support for VLIW until fairly recently, and it has...

...c Christopher [mailto:echristo at gmail.com] > Sent: Friday, June 13, 2014 4:32 PM > To: Sergei Larin > Cc: David Blaikie; LLVM Developers Mailing List > Subject: Re: [LLVMdev] Looking for a fix to memory leak in DWARF support > > On Fri, Jun 13, 2014 at 2:28 PM, Sergei Larin <slarin at codeaurora.org> wrote: > > > > Thanks Eric, > > > > > > They are doing LTO build but with some custom modifications (think a > library at a time as opposed to a whole program). I must admit, it is a rather > large application as well, so as expected, any in...

...legal IR. With this in mind, the correct behavior for CloneFunction is to not remap any debug metadata (and just attach the original nodes) if it is cloning into the same Module *and* there is not DISubprogram attached to the function. -- adrian > On Jun 20, 2017, at 7:52 AM, Sergei Larin <slarin at codeaurora.org> wrote: > > Adrian, > > Thank you for the explanation. The example is produced by yet another pass and I will further debug it there... > > Nevertheless, should it not the deep copy of debug locations (once it has created the new DICompileUnit) updated th...

...Christopher [mailto:echristo at gmail.com] > Sent: Friday, June 13, 2014 4:00 PM > To: Sergei Larin > Cc: David Blaikie; LLVM Developers Mailing List > Subject: Re: [LLVMdev] Looking for a fix to memory leak in DWARF support > > On Fri, Jun 13, 2014 at 11:03 AM, Sergei Larin <slarin at codeaurora.org> wrote: > > > > David, > > > > Thanks for the quick response... > > > > > > No, at this point I am just getting into the issue... I assume it is a leak, but > no clear proof yet. I was hoping it was an obvious thing since I recall a...

...fixed) my share of bugs in debug info). > > Best you start with a leak tracking tool and at least be able to point to the > major leak culprit (eg: "90% of the leaked memory was allocated at <stack > trace>") > > On Fri, Jun 13, 2014 at 9:16 AM, Sergei Larin <slarin at codeaurora.org> wrote: > > > > David, (and everyone else) > > > > I am forced to do some maintenance work on a fairly old LLVM branch > > (likely based on release 3.1) that among other issues has a major > > problem with memory leak somewhere around DWARF...

...nto the same LLVM module the CU should not cloned. If don't mind sharing your code, I can try to help diagnose why the CU gets cloned... just send me a patch that applies to trunk and instructions. >> >> -- adrian >> >>> On Jun 16, 2017, at 1:54 PM, Sergei Larin <slarin at codeaurora.org> wrote: >>> >>> Sorry… It takes a pass that was not accepted for upstreaming…. It uses CloneFunctionInto with module level flag on. In the input IR there is a strangely formed (but correct) debug info MD that causes duplication of existing DICompileUnit durin...

Peter, I am afraid I am missing a big picture with debug info cloning. Certainly after your patch (and possibly in some cases earlier): Cloning: Reduce complexity of debug info cloning and fix correctness issue. Commit r260791 contained an error in that it would introduce a cross-module reference in the old module. It also introduced O(N^2) complexity in the

...gt; From: Dan Gohman [mailto:gohman at apple.com] > Sent: Friday, August 10, 2012 12:30 PM > To: Sergei Larin > Cc: 'Triple Yang'; llvmdev at cs.uiuc.edu > Subject: Re: [LLVMdev] VLIW code generation for LLVM backend > > > On Aug 9, 2012, at 10:09 AM, Sergei Larin <slarin at codeaurora.org> > wrote: > > > Yang, > > > > This might not be such a tough choice on engineering side - one of > > the LLVM differentiators is the ground-up, early introduced support > > for VLIW specific features. > > Actually, LLVM lacked suppor...

...; -----Original Message----- > From: Chris Lattner [mailto:clattner at apple.com] > Sent: Sunday, September 20, 2015 5:28 PM > To: Sergei Larin > Cc: llvm-dev at lists.llvm.org; Lang Hames > Subject: Re: GlobalOPT and sections > > On Sep 18, 2015, at 10:45 AM, Sergei Larin <slarin at codeaurora.org> wrote: > > What I do not see - the section information from the original GV is never > copied to the NewGV, so this test would be failing for me: > > Now the proverbial question - is this a bug or a feature? ...and if it was > meant to be done that way then...

The if you are cloning into the same LLVM module the CU should not cloned. If don't mind sharing your code, I can try to help diagnose why the CU gets cloned... just send me a patch that applies to trunk and instructions. -- adrian > On Jun 16, 2017, at 1:54 PM, Sergei Larin <slarin at codeaurora.org> wrote: > > Sorry… It takes a pass that was not accepted for upstreaming…. It uses CloneFunctionInto with module level flag on. In the input IR there is a strangely formed (but correct) debug info MD that causes duplication of existing DICompileUnit during cloning, but l...

Can you send me a patch with instructions to reproduce? I can take a look. -- adrian > On Jun 15, 2017, at 2:23 PM, Sergei Larin <slarin at codeaurora.org> wrote: > > Yes, it does for us. My tree is couple days off the tip, and I see it there. > > Sergei > > From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of Keno Fischer via llvm-dev > Sent: Thursday, June 15, 2017 1:25 PM > To: A...

Hi Sergei. If an instruction conditionally writes R0 then I think it needs to implicitly use R0 for proper liveness Andy On Aug 9, 2012, at 9:48 AM, Sergei Larin <slarin at codeaurora.org> wrote: > > Hello everyone, > > Let me (re)present a question that might have previously been discussed, > but did not result in any code (AFIK). > > How do we represent a _conditional_ assignment (def) in a bundle MI? > > More contents - curr...

Hello everyone, I am working on a release based on the branch 3.1 version of code. Unfortunately it has enough differences that exact rev does not apply. I am hitting an assert in liveness update with seemingly trivial code (attached). /local/mnt/workspace/slarin/tools/llvm-mainline-merged/lib/CodeGen/LiveInter valAnalysis.cpp:1078: void llvm::LiveIntervals::HMEditor::moveAllRangesFrom(llvm::MachineInstr*, llvm::SlotIndex): Assertion `validator.rangesOk() && "moveAllOperandsFrom broke liveness."' failed. The code being scheduled (func...

On Sat, Apr 27, 2013 at 7:26 PM, Nick Lewycky <nicholas at mxc.ca> wrote: > On 04/26/2013 04:20 PM, Owen Anderson wrote: > >> >> On Apr 26, 2013, at 3:07 PM, Sergei Larin <slarin at codeaurora.org >> <mailto:slarin at codeaurora.org>**> wrote: >> >> Dan, >>> Thank you for the quick and throughout reply. First paragraph pretty >>> much sums it up. Unless there is more will to guaranty (or provide >>> under flag) stricter...

...it did not surface. Thanks for any leads and/or suggestions. Sergei --- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation From: David Blaikie [mailto:dblaikie at gmail.com] Sent: Friday, April 15, 2016 2:38 PM To: Sergei Larin <slarin at codeaurora.org> Cc: llvm-dev <llvm-dev at lists.llvm.org> Subject: Re: [llvm-dev] Dangling debug value or bug in argument elimination pass? Unclear. It's going to be awkward for debug info regardless (describing the variable is important to name lookup, describing the parameter&...

On Jun 12, 2012, at 10:22 AM, Sergei Larin <slarin at codeaurora.org> wrote: > > Hello everyone, > > I am working on a release based on the branch 3.1 version of code. > Unfortunately it has enough differences that exact rev does not apply. > I am hitting an assert in liveness update with seemingly trivial code > (attach...

...s now the only drawback is its poor support for VLIW architecture. And so if we can count on LLVM's support for VLIW in a near future, we will choose LLVM as the compiler infrastructure without the least hesitation. Can I do any help for this underway work? Regards. 2012/8/8 Sergei Larin <slarin at codeaurora.org>: > Yang, > > There is work currently underway to add SW pipelining and some sort of > global scheduling to Hexagon, but if there is some interest to it from other > targets, it would be helpful to know. What is your involvement with this? > > Sergei Lari...