similar to: [GSoC 2018] Application - Improve Debugging of Optimized Code

Thanks Anastasis. This proposal looks good to me, this is great work. @all, here is a link to the project description: https://llvm.org/OpenProjects.html#llvm_optimized_debugging Davide (CC'd) and I will be available as mentors. I'd be happy to help answer any questions/concerns about this project. vedant > On Mar 16, 2018, at 11:07 AM, Anast Gramm <anastasis.gramm2 at

FWIW, I've raised the LICM issue here: https://bugs.llvm.org/show_bug.cgi?id=37682 On 31 May 2018 at 13:28, Anast Gramm <anastasis.gramm2 at gmail.com> wrote: > Thanks, > These are very helpful. > > As I understand it, SROA and LICM render some variables > "useless" by optimizing the code to not use them. Hence we can't debug > them. > >

Hello, I'm an undergraduate student in the CS department of Aristotle University of Thessaloniki (AUTh). Last year I successfully completed GSoC with Mixxx [1] and this year I would like to work on LLVM. I am interested in "Improving debugging of optimized code" [2]. I have gone through the kaleidoscope tutorial and I've set up a basic dev environment for LLVM and clang.

Many DI-related bugs are caused by missing Debug Location in an instruction created in a transformation. Most of the time the fix is trivial once you found where the culprit instruction is created (https://reviews.llvm.org/D50263). Currently, when you create a new Instruction, in order to give it DL you have to either use an IRBuilder that is previously set to the correct DL or “manually” create

Hello, My proposal for GSoC 2018 [attachment] about improving debugging of optimized code was accepted. I will work with my mentor Vedant Kumar (vsk) through the summer to find where DI loss occurs and try to fix as many occurrences as possible. I will also be keeping a devlog here: https://gramanas.github.io/ You can check what the first steps of my project are on the latest post:

> That is good to hear / expected, since we went though great lengths to ensure that SROA preserves variable debug info. > > Have you looked at the location-less phi instructions? > Does empty mean line 0 or do you mean they have no debug location whatsoever? Most of them have line 0, only 12 are locationless. > Are they empty for good reasons or does it look more like an

Welcome Anastasis! I'm very happy to see this work going forward. I see that your first task is to make "debugify" into a function pass, so we will be able to get data on a per-pass basis. At EuroLLVM there was a relevant lightning talk about a different tool, see: http://llvm.org/devmtg/2018-04/talks.html#Lightning_11 It will be extremely interesting to see how well your results

> > is in the business of deciding, but it does score it as a difference > because it now, at no point, sees the expression "first" evaluate to a > value of 5, or "total" to a value of 8 which it did previously. From the > source-level debugging experience, the variables now just get updated > between iterations. > Obviously should've been 7 for that

Hi Anastasis, Welcome, and congratulations! It's great to see that you're maintaining a devlog and have hit the ground running. I'm looking forward to working with you. > On Apr 25, 2018, at 12:56 PM, via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Welcome Anastasis! I'm very happy to see this work going forward. > > I see that your first task is to

Introduction ============ `SROA' is an early stage pass running at the very beginning of the pipeline in `-O{1,2,3}'. Greg Bedwell's report from his DExTer tool shows SROA on function as one of the major culprits of Debug Info loss. With debugify-each partially done I tried testing this on the amalgamated sqlite source. The steps are as follows: ,---- | # generate

> On May 30, 2018, at 8:37 AM, Anast Gramm <anastasis.gramm2 at gmail.com> wrote: > > Introduction > ============ > > `SROA' is an early stage pass running at the very beginning of the > pipeline in `-O{1,2,3}'. Greg Bedwell's report from his DExTer tool > shows SROA on function as one of the major culprits of Debug Info > loss. > > With

Hi all, I am running samba 3.0.6 on Linux and am wondering if anyone knows if it is possible to delete a print driver from the driver database? I have around 20 printers running off of this print server and occasionally we remove all of a certain type of printer. Also, for some reason, the drivers sometimes seem to become corrupt and it would be nice to be able to entirely remove a driver and

Hello, > On Apr 26, 2018, at 6:44 AM, Son Tuan VU <sontuan.vu119 at gmail.com> wrote: > > Hi Vedant, > > I have tried to implement the fix you proposed, but it didn't work as expected. I created a new Module Pass Manager (not Function Pass Manager) and override the add() method like this: > > class DebugifyEachPassManager : public legacy::PassManager { >

Hi Vedant, Thank you for your reply. I think I can make this debugify-each mode, but I guess this is reserved for your GSoC project ? However, if I understand correctly, we do not want to take the output of the first check-debugify (I mean the .ll file with potentially all the WARNINGs and ERRORs after the first pass) as input for the second debugify. What we need is to take the fresh output of

I must be missing something, because I can't believe that there haven't been any updates since July 27 9fa12aadcd2ea45fdcb91bd125b619545993defa2032cf99b8a89cf6099723e8-primary.xml.gz 27-Jul-2017 15:12 4.0M [ ] 23b0e14a9667597b69a8719f0eea709721cc32f9f3b6c8202da0f5a36b9f1759-other.xml.gz 27-Jul-2017 15:12 137M [ ]

Mhm I see now, thanks for your explanation! Son Tuan Vu On Fri, Mar 16, 2018 at 10:58 PM, Vedant Kumar <vsk at apple.com> wrote: > > On Mar 16, 2018, at 2:30 PM, Son Tuan VU <sontuan.vu119 at gmail.com> wrote: > > Hi Vedant, > > Thank you for your reply. I think I can make this debugify-each mode, but > I guess this is reserved for your GSoC project ? > >

Hi Vedant, hi all, My goal is to measure debug info loss of *each* optimization pass in LLVM. I am trying to create a debugify-each mode in opt, inspired by verify-each mode which is supposed to already work. However, if I understand correctly, the verify-each mode (triggered by -verify-each option in opt) only works when we provide a pass list or a pass pipeline. Is this intended? I mean, why

I've been searching around for a couple of days, and I just can't seem to find the answer I'm looking for. I have a 6.x box that I use as my gateway firewall. It has three NICs; 1 external, 1 internal, 1 for a guest network. I have various inbound traffic routed to separate internal machines based on the application (ie. http, smtp, ftp, etc....). All works well, but I'd

> -----Original Message----- > From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of Nicolas > Kovacs > Sent: Thursday, September 14, 2017 3:34 PM > To: centos at centos.org > Subject: Re: [CentOS] Running COS 7.1708 on VirtualBox 5.1.28 > > Le 14/09/2017 ? 21:32, Ken Gramm a ?crit?: > > Anyone else having issues getting the VB drivers to load on 1708? >

Hi all, I am running samba 3.0.6. I am having an issue on my print server regarding how the printer ends up registering itself on the Windows clients. We have a machine named "bob", "bob" has an alias both in DNS and in the netbios name in Samba of "printserver", "bob" has an IP address of 192.168.1.1. In a seemingly random fashion sometimes when I add