search for: raghesh

Is your case the case mentioned in the subject or a different case? ~Craig On Sun, Jan 5, 2020 at 8:11 PM raghesh <raghesh.a at gmail.com> wrote: > Thanks Sanjay for your comments. > > So, if we want to add a transformation avoiding the one-use check, which > one is the ideal pass? Shall we do it in -aggressive-instcombine? I came > to know that if the pattern search complexity is O(n) [1...

...r of > instructions. If X/Y has another use other than this one, then it still > ends up being calculated. Without the one use check you'd trade 2 fdivs, > for 1 mul (Y * Z), and 2 fdivs ((X*Y)/Z) and the original (X / Y). > > ~Craig > > > On Mon, Dec 30, 2019 at 4:07 PM raghesh via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> Dear All, >> >> The InstCombine pass performs the following transformation. >> >> Z / (X / Y) => (Y * Z) / X >> >> This is performed only when operand Op1 ( (X/Y) in this case) has o...

...rformance-wise) if we avoid the m_OueUse check. What if we perform the transformation even if there are multiple uses? There are similar transformations which perform the m_OueUse check. We may avoid those too if there is no particular reason for the check. Regards, ------------------------------ Raghesh Aloor AMD India Pvt. Ltd. Bengaluru. ------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20191231/2cdbce17/attachment.html>

Hi All, We set up a Polly buildbot tester and would like to add this to LLVM buildbots. We want to commit the buildbot scripts to the LLVM/zorg repository and include buildslave to buildbot.llvm.org Can any one help us to do this? Regards, -- Raghesh

...en with `undef`. As it mentioned, "on" a 'lifteime.start', we are unsure about if it is meant to be before or after it. Will there be any issue in later passes, if we have an "undef" value "store" after lifetime.start. Regards, ------------------------------ Raghesh Aloor AMD India Pvt. Ltd. Bengaluru. ------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20190924/afdf1db4/attachment.html>

Dear all, I am Raghesh, a student pursuing M.Tech at Indian Institute of Technology, Madras, India. I would like to make contribution to the Polly project (http://wiki.llvm.org/Polyhedral_optimization_framework) as part of GSOC 2011. I have gained some experience working in OpenMP Code generation for Polly. This is almo...

Hi, raghesh and I are working in Polly on automatically generating OpenMP calls. This works nicely on a 64bit architecture, however the functions we need to generate are slightly different on different platforms. The reason for the difference is that e.g "long" in > bool GOMP_loop_runtime_nex...

...at most 1 positional arguments: See: llc -help > In case this does not work, I will investigate this on an i386 machine. > All our development machines are amd64 machines and I must admit we did > not test too much on i386. So issues on those machines are not too > unexpected. Though Raghesh runs i386. He may have seen such a problem > before. I see. I will try it amd64 version but now on VMWare. I'm glad if you tell me your environment in detail. > Cheers and thanks for your report > Tobi > > > > -- Tomohiro moriyama at isit.or.jp

...mp; gcc out.s && ./a.out >> In case this does not work, I will investigate this on an i386 machine. >> All our development machines are amd64 machines and I must admit we did >> not test too much on i386. So issues on those machines are not too >> unexpected. Though Raghesh runs i386. He may have seen such a problem >> before. > > I see. I will try it amd64 version but now on VMWare. > I'm glad if you tell me your environment in detail. Basically I have an Ubuntu amd64. So if you just want to go ahead with some experiments I would us an 64bit oper...

...ro at ubuntu:~$ >>> In case this does not work, I will investigate this on an i386 machine. >>> All our development machines are amd64 machines and I must admit we did >>> not test too much on i386. So issues on those machines are not too >>> unexpected. Though Raghesh runs i386. He may have seen such a problem >>> before. >> >> I see. I will try it amd64 version but now on VMWare. >> I'm glad if you tell me your environment in detail. > > Basically I have an Ubuntu amd64. So if you just want to go ahead with > some experim...

hi raghesh, > > 5. Porting Polly to Various architectures. > ------------------------------------------------- > > Currently Polly generates everything as 64 bit integer, which is > problamatic for embedded platforms. > you may try something like this: http://lists.cs.uiuc.edu/pipermail...

On Wed, Dec 22, 2010 at 01:38:06PM -0500, Tobias Grosser wrote: > Hi, > > raghesh and I are working in Polly on automatically generating OpenMP > calls. This works nicely on a 64bit architecture, > however the functions we need to generate are slightly different on > different platforms. > > The reason for the difference is that e.g "long" in > &g...

...;> In case this does not work, I will investigate this on an i386 > machine. > >>> All our development machines are amd64 machines and I must admit we > did > >>> not test too much on i386. So issues on those machines are not too > >>> unexpected. Though Raghesh runs i386. He may have seen such a > problem > >>> before. > >> > >> I see. I will try it amd64 version but now on VMWare. > >> I'm glad if you tell me your environment in detail. > > > > Basically I have an Ubuntu amd64. So if you just want...

...the llc compiler and than gcc to statically compile the binary. In case this does not work, I will investigate this on an i386 machine. All our development machines are amd64 machines and I must admit we did not test too much on i386. So issues on those machines are not too unexpected. Though Raghesh runs i386. He may have seen such a problem before. Cheers and thanks for your report Tobi

...; >>>> In case this does not work, I will investigate this on an i386 machine. >>>> All our development machines are amd64 machines and I must admit we did >>>> not test too much on i386. So issues on those machines are not too >>>> unexpected. Though Raghesh runs i386. He may have seen such a problem >>>> before. >>> >>> I see. I will try it amd64 version but now on VMWare. >>> I'm glad if you tell me your environment in detail. >> >> Basically I have an Ubuntu amd64. So if you just want to go ahea...

On 04/04/2011 12:23 AM, Vlad Krylov wrote: > > Hi. Hi Vlad, first of all it seems the conflict with raghesh was already solved. Nice. Regarding your draft. It looks like a reasonable first version, but it obviously needs to be extended for the final application. I would also recommend to install Polly and try to find the first test cases that cannot be handled. Some comments to your work plan: >...

H, Tobias Thank you for your reply. Tobias Grosser wrote: (Thu, 09 Jun 2011 15:41:05 -0300) >On 06/08/2011 01:17 AM, MORIYAMA Tomohiro wrote: >> Hi, all >> >> I tried Polly installation on Ubuntu. >> >> On its building, it returned no errors. >> But when I run "make polly-test", it returns 11 unexpected failures as >> follows. >>

Hi. My plan would be: 1w Study sources of Polly and LLVM docs relating to analysis. 2w Create tests which demonstrate problems with NSW/NUW 3-4w Fix the handling of wrap overflows. 5w Complete middle term paperwork. 6w Create tests for each of cases which are not currently optimized (e.g. have min/max, sext/zext, trunc or unsigned comparisons in the loop bounds or memory accesses). 7w Learn how

Hi, as raghesh already posted in a previous mail, we would like to add some Polly buildslaves to the buildmaster. I just finished to set up the buildslave and now need someone to add my password to the config files. As Daniel seems to be on leave, I wonder who else has access to this machine? Cheers and than...

On 03/23/2011 09:58 PM, ether zhhb wrote: > hi raghesh, > > >> >> 5. Porting Polly to Various architectures. >> ------------------------------------------------- >> >> Currently Polly generates everything as 64 bit integer, which is >> problamatic for embedded platforms. >> > you may try something like...