search for: anastasis

Hello, I submitted a draft proposal at the gsoc website. You can see the application in the attached pdf. Any feedback is welcome. thanks, Anastasis -------------- next part -------------- A non-text attachment was scrubbed... Name: GSoC2018_llvm_application.pdf Type: application/pdf Size: 41454 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180316/273ef464/attachment-0001.pdf>

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. vedan...

...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: https://gramanas.github.io/posts/community-bonding/ I'd love to hear any thoughts or questions you might have. Cheers, Anastasis -------------- next part -------------- A non-text attachment was scrubbed... Name: GSoC2018_llvm_final.pdf Type: application/pdf Size: 41291 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180425/50cc7b54/attachment-0001.pdf>

...e drivers sometimes seem to become corrupt and it would be nice to be able to entirely remove a driver and then reinstall it from scratch. Is this a possible thing to do? Thanks, Chris ________________________________________________________________________ ________ Chris Slack IT Manager M/V Anastasis - Currently docked in Bremerhaven, DL Mercy Ships <mailto:chris.slack@mercyships.org> chris.slack@mercyships.org <http://www.mercyships.org/> www.mercyships.org <http://www.chrisslack.org/>

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/tal...

Hello, @Anastasis: what do you think about this? Do you mind if I implement the debugify-each mode and refactor the code to have DebugifyFunctionPass and DebugifyLoopPass? I am sorry if it bothers you, I should have done this earlier, so you could focus on fixing the optimization passes. FYI, my debugify-each is qui...

...} > }; > > However, we can't apply and check debugify of FunctionPasses since these passes are managed by Function Pass Managers created on the fly during schedulePass(). I guess we'd have to implement the FunctionPass version of Debugify and CheckDebugify. Yes, Anastasis (CC'd) has started exploring this idea: https://gramanas.github.io/posts/community-bonding/ <https://gramanas.github.io/posts/community-bonding/>. Please sync up with him before you start hacking, so you can collaborate on the design and split up work :). Now that GSoC has officially star...

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...

...sult, which does sometimes occur). Does anyone have an idea why this might be occurring? Is it a common problem with Samba or do we have something setup wrong somewhere? Thanks, Chris ________________________________________________________________________ ________ Chris Slack IT Manager M/V Anastasis - Currently docked in Bremerhaven, DL Mercy Ships <mailto:chris.slack@mercyships.org> chris.slack@mercyships.org <http://www.mercyships.org/> www.mercyships.org <http://www.chrisslack.org/>

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. > > -------------- next part -------------- An HTML...

...wrote: >> >> 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. >> >> >> + Anastasis, who's interested in working on this as well. There's >> definitely enough work to go around: once we can measure debug info loss >> after each pass, we'll need a testing harness. >> >> >> However, if I understand correctly, the verify-each mode (triggered...

...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. >>> >>> >>> + Anastasis, who's interested in working on this as well. There's >>> definitely enough work to go around: once we can measure debug info loss >>> after each pass, we'll need a testing harness. >>> >>> >>> However, if I understand correctly, the verify-e...

...oject) I would appreciate it. I would also like some more information about the first goal of the project, like an outline of the procedure you have in mind for gathering debug loss metrics. I'll be in llvm's IRC with the nick "gramanas" in case you want to PM me. Best regards, Anastasis [1] https://mixxx.org/wiki/doku.php/crate_enhancements [2] https://llvm.org/OpenProjects.html#llvm_optimized_debugging

...ad this problem and like I said, everything else is working fine. Attached to the bottom of this message is a dump from testparm with the details of my /etc/samba/smb.conf file. Please let me know if anyone can give me any suggestions. Thanks, Chris Slack IT System Administrator Mercy Ships M/V Anastasis - Currently docked in Freetown, Sierra Leone, West Africa www.mercyships.org ---------------------------------------------------------------------------- -------------------------------------------------------- [root@herm2 /etc]# testparm Load smb config files from /etc/samba/smb.conf Processing...

...U <sontuan.vu119 at gmail.com> wrote: > > 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. > > > + Anastasis, who's interested in working on this as well. There's > definitely enough work to go around: once we can measure debug info loss > after each pass, we'll need a testing harness. > > > However, if I understand correctly, the verify-each mode (triggered by > -verify-each...

..., at 8:11 AM, Son Tuan VU <sontuan.vu119 at gmail.com> wrote: > > 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. + Anastasis, who's interested in working on this as well. There's definitely enough work to go around: once we can measure debug info loss after each pass, we'll need a testing harness. > However, if I understand correctly, the verify-each mode (triggered by -verify-each option in opt) only wo...

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

...sontuan.vu119 at gmail.com>> wrote: >> >> 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. > > + Anastasis, who's interested in working on this as well. There's definitely enough work to go around: once we can measure debug info loss after each pass, we'll need a testing harness. > > >> However, if I understand correctly, the verify-each mode (triggered by -verify-each option i...

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

> 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