similar to: We really need more community involvement with GSoC

I would like to insist more to use slack.com due to persistent storage of message it can be useful to create 'Minutes of Meeting' kind of thing and later on shared on mailing list so that all community can be aware of that, when some serious discussion has happened during 'office hours'. *Vivek Pandya* On Sun, Mar 20, 2016 at 1:53 AM, Chandler Carruth <chandlerc at

@James I am not sure in IRC if we can retrieve back the older messages. So consider Slack as suggestion only. *Vivek Pandya* On Sun, Mar 20, 2016 at 6:29 PM, James Molloy <james at jamesmolloy.co.uk> wrote: > Hmm. But we already use IRC, we don't already use Slack (as a community). > > On Sun, 20 Mar 2016 at 10:57, vivek pandya <vivekvpandya at gmail.com> wrote: >

I think the idea of dedicated "newbie hour - no question is too basic" drop in sessions is fantastic. +1 for that. On Sat, 19 Mar 2016 at 11:26 Bruce Hoult via llvm-dev < llvm-dev at lists.llvm.org> wrote: > I work for one of those "top companies", but LLVM is only one of the > back-ends I'm working with so I have only pretty narrow knowledge of it > (but

Hi, Indeed, and I think this suggestion will succeed best if the delta between what community members do now and what they would need to do is small. Loitering on one extra IRC room is trivial; loading a whole new system just at the right time is likely to get fewer members. James On Sun, 20 Mar 2016 at 14:47, Bruce Hoult <bruce at hoult.org> wrote: > IRC doesn't archive messages,

On 3/19/16 6:26 AM, Bruce Hoult via llvm-dev wrote: > I work for one of those "top companies", but LLVM is only one of the > back-ends I'm working with so I have only pretty narrow knowledge of > it (but ok knowledge of compilers in general, I hope). > > I'm trying to post easy to understand answers to those beginner > questions when I have time (there was

On 03/20/2016 12:20 PM, John Criswell via llvm-dev wrote: > On 3/19/16 6:26 AM, Bruce Hoult via llvm-dev wrote: >> I work for one of those "top companies", but LLVM is only one of the >> back-ends I'm working with so I have only pretty narrow knowledge of >> it (but ok knowledge of compilers in general, I hope). >> >> I'm trying to post easy to

Hello Community, I have submitted my draft proposal for this project on the summer of code web site and shared it with the community. Please take a look at it and suggest/ comment some modifications. I have already done some study on the relevant code. I will still do some more before the final submission but this is more of designing challenge please help ! Sincerely, *Vivek Pandya*

Hello Matthias Reisinger, It is simple html page that shows simple abstract ( which I have already added for all projects as per GSoC page) , link to your read-only proposal, blog URL (if you maintain any) , and status reporting interval (if you want to follow) and any other relevant information. You can check out (SVN) related code here http://llvm.org/svn/llvm-project/www/trunk/SummerOfCode/

Apologies: didn't notice how old this thread is before replying. On Tue, Mar 22, 2016 at 5:24 PM, Sanjoy Das <sanjoy at playingwithpointers.com> wrote: > Hi Vivek, > > [+CC Matthias, Quentin] > > Inter-procedural register allocation can be a big win, but my estimate > is that it will be challenging to complete within one summer unless > you're already familiar

Thank you Vivek, I posted an according patch on phabricator. I also took the liberty to change the design a little bit (based on the open projects page http://llvm.org/OpenProjects.html). But take it with a grain of salt, I'm no html expert :) Best regards, Matthias Am Dienstag, 10. Mai 2016 19:48:21 UTC+2 schrieb vivek pandya: > > > > *Vivek Pandya* > > > On Tue, May

Hi Vivek, [+CC Matthias, Quentin] Inter-procedural register allocation can be a big win, but my estimate is that it will be challenging to complete within one summer unless you're already familiar with LLVM's register allocator. I've CC'ed some people who can give you some more detailed information. -- Sanjoy On Tue, Feb 9, 2016 at 9:17 PM, vivek pandya via llvm-dev

Hello Quentin, I see your work on shrink-wrapping optimization at http://reviews.llvm.org/rL236507 IPRA has benefited shrink-wrapping optimization ( I have noticed that on sqlite3 test-case) so I did read Fred Chow's paper and compare that approach with yours I did not understand much of your work :-( in comparison to original paper but I feel that current approach is not generating same

No need to apologize this thread surely deserved some answers :) From my perspective this project sounds doable. I would expect the register allocation parts to be not too hard: I imagine this being just distilling a new clobber regmask after allocating a function. I would expect the challenging (or annoying) part to get a machine module pass (or a similar mechanism to influence the order in

The pass manager already has support for calligraph connected region IIRC. As for the regmask part, we probably could hack something up in a week or so, but I believe this is not what Vivek had in mind. I think the main challenge of a real inter-procedural register allocator is to change all of the calling convention dynamically and more importantly convey the right information to other tools

Hello LLVM Community, I am interested doing following project with LLVM for GSoC 2016. Code Generation Improvements: Particularly Generalize target-specific backend passes that could be target-independent I have done some initial study and try to understand the task to be done. Please help me to develop the proposal. Following are my initial findings : 1. lib/Target/Hexagon/RDF* : Code

*Vivek Pandya* On Wed, Mar 23, 2016 at 9:43 AM, C Bergström <cbergstrom at pathscale.com> wrote: > From the research and code I've seen - Doesn't this break regalloc > down into a global and location allocation strategy? (maybe I'm > remembering incorrectly) > > Yes I think you are correct. If I recall IP Reg allocation allocates some registers to varibale that

The Drupal project announced several security vulnerabilities for the 4.7.x and 5.x releases of the Drupal package. These effect two current ports: www/drupal4 and www/drupal5. The following are the security advisories that were posted: 4.7.x: * DRUPAL-SA-2007-024: http://drupal.org/node/184315 * DRUPAL-SA-2007-026: http://drupal.org/node/184320 * DRUPAL-SA-2007-030:

Hello Ethan, > Hi Vivek, > > I've reviewed your MachineModulePass proposal and in general, I like > what I'm seeing. A few suggestions on how you can make it stronger: > > 1. Please go into more specific detail on your prior work with LLVM. > Specifically: > 1. Which optimizations and passes have you implemented in your > class assignments?

> On Mar 22, 2016, at 6:04 PM, Matthias Braun via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > No need to apologize this thread surely deserved some answers :) > > From my perspective this project sounds doable. I would expect the register allocation parts to be not too hard: I imagine this being just distilling a new clobber regmask after allocating a function. I would

----- Original Message ----- > From: "vivek pandya" <vivekvpandya at gmail.com> > To: "Matthias Braun" <matze at braunis.de> > Cc: "Hal Finkel" <hfinkel at anl.gov>, "llvm-dev" > <llvm-dev at lists.llvm.org> > Sent: Wednesday, May 11, 2016 1:14:07 PM > Subject: Re: [llvm-dev] [GSoC 2016] Interprocedural Register