similar to: Help regarding a project:

Dear everyone, I am current working on a project that requires me to divide an integer into two halves based on its bits and carry out multiplication and addition on the new data and combine these results to get the original result. Could someone please help with the "how to" part. Thanking you, Vivek Datir IIT Guwahati , India -------------- next part -------------- An HTML

Water engineer here. The standard approach is to 1) get the storage vs. elevation data from the designers of the reservoir or, barring that, 2) get the bathymetry data from USBR or state DWR, or, if available, get the DEM data from USGS if the survey was done before the reservoir was built or 3) get a boat+sonar with GPS? +lots of time and survey the bottom elevation yourself. Put the xyz

Dear all; Thank you for your reply. David has explained an interesting method. David I have DEM file of the region and I have extracted the xyz data from that. Also I can extract bathymetry data as xyz file. I have calculated the storage (volume) of reservoir at the current elevation. But the method I have used to calculate the volume is different from your method. I have crop DEM by the reservoir

Hello All, Eric Langley here with my first post to this list. I am looking to determine if R is suitable for a development project I am working on and if so possibly finding someone proficient in R that would be interested in doing the coding. I would like to preface my inquiry that while I am not a programmer I can communicate in a dialog my objectives. An array of rank ordered data looks like

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

*Vivek Pandya* On Wed, Mar 23, 2016 at 10:18 PM, Quentin Colombet <qcolombet at apple.com> wrote: > The pass manager already has support for calligraph connected region IIRC. > If I am not wrong Quentin and Mehdi Amini refers to CallGraphSCCPass.cpp > 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

*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

Thanks Dylan, I am working on a backend which has mulhsu instruction that performs multiplication between signed and unsigned number and returns upper 32 bits into result register. I think I also need to write some code probably as you indicated to check signedness of the operands and based on that lower to mulhsu instruction. -Vivek On Mon, Feb 27, 2017 at 11:13 AM, Dylan McKay <me at

>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) On Wed, Mar 23, 2016 at 12:04 PM, Mehdi Amini via llvm-dev <llvm-dev at lists.llvm.org> wrote: > >> On Mar 22, 2016, at 6:04 PM, Matthias Braun via llvm-dev <llvm-dev at lists.llvm.org> wrote: >>

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

> On May 5, 2017, at 8:49 AM, Hal Finkel <hfinkel at anl.gov> wrote: > > > > On 05/05/2017 10:44 AM, vivek pandya via llvm-dev wrote: >> Hello LLVM Devs, >> >> I have an idea to improve effectiveness of IR dump with -emit-after-all based on Adam Nemet's 2016 LLVM Dev presentation. >> I think we can track changes in each function, basic block and

One more interesting thing I have noticed is as following : In sqlite3 code consider 3 functions namely sqlite3Update, sqlite3Select and sqlite3Where begin sqlite3WhereBegin is called by both functions sqlite3Update and sqlite3Select but according to CallGraphSCC sqlite3Update is codegen before in that case during RegMask propagation phase default regmask is used for call site of

I think your users will be very upset if you don't set the boolean return value correctly :-) Whatever work it takes to determine the correct value for it, if the user code doesn't need/use that value then the dead code will be eliminated later. But if they need that return flag then they will want it to be correct! You may need to use a multiply instruction that returns a

> On Mar 24, 2016, at 1:00 PM, Pete Cooper via llvm-dev <llvm-dev at lists.llvm.org> wrote: > >> >> On Mar 24, 2016, at 11:09 AM, Pete Cooper <peter_cooper at apple.com <mailto:peter_cooper at apple.com>> wrote: >> >>> >>> On Mar 23, 2016, at 6:38 PM, Gerolf Hoflehner via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at

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

*Vivek Pandya* On Fri, Mar 25, 2016 at 1:30 AM, Pete Cooper <peter_cooper at apple.com> wrote: > > On Mar 24, 2016, at 11:09 AM, Pete Cooper <peter_cooper at apple.com> wrote: > > > On Mar 23, 2016, at 6:38 PM, Gerolf Hoflehner via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > > On Mar 23, 2016, at 2:59 PM, Quentin Colombet via llvm-dev <

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

On Tue, Jun 21, 2016 at 12:31 AM, Matthias Braun <matze at braunis.de> wrote: > I just discussed this with vivek on IRC (and I think we agreed on this): > > Let me first state the motivation clearly to ease later discussions: > As far as the motivation for this change goes: Changing the calling > convention allows us to choose whether a register is saved by the callee or >

On Tue, Jun 21, 2016 at 8:58 PM, John Criswell <jtcriswel at gmail.com> wrote: > On 6/20/16 11:29 PM, Mehdi Amini wrote: > > > On Jun 20, 2016, at 11:12 AM, John Criswell via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > On 6/20/16 9:39 AM, vivek pandya via llvm-dev wrote: > > Dear Community, > > To improve current interprocedural register

> On Jun 20, 2016, at 11:12 AM, John Criswell via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On 6/20/16 9:39 AM, vivek pandya via llvm-dev wrote: >> Dear Community, >> >> To improve current interprocedural register allocation (IPRA) , we have planned to set callee saved registers to none for local functions, currently I am doing it in following way: