search for: christudasan

Displaying 8 results from an estimated 8 matches for "christudasan".

2020 May 30
2
Dynamically determine the CostPerUse value in the register allocator.
...s misnomer for what it is intended. At first sight, the word indicates that the cost is a function of uses of the register - more the uses more the cost. How do we want to define the value of CostPerUse. Should it be a function of uses? or just the target? On Sat, May 30, 2020, 4:53 PM Devadasan, Christudasan via llvm-dev < llvm-dev at lists.llvm.org> wrote: > [AMD Official Use Only - Internal Distribution Only] > > > > Please ignore the header “AMD Official Use Only”. I forgot to remove it > while posting the email to llvm-dev. > > > > Regards, > > Christudasa...
2020 May 29
2
Dynamically determine the CostPerUse value in the register allocator.
...unction calls, the register cost is unnecessary. Because there is no ABI for such kernel programs. It caused a performance penalty for such kernels due to the register cost. That's the exact reason we need a method to determine dynamically either to have a reg-cost or not to have one. Regards, Christudasan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200529/d1e02e10/attachment.html>
2017 Jul 13
2
Question about thinLTO
On Thu, Jul 13, 2017 at 8:37 AM, Christudasan D <xander.cd at gmail.com> wrote: > > Hi Teresa, > > Yes, we plan to have our code at CG directly. > We use our own linker. That's the pain. We might only get a partial > benefit of thinLTO which occurs at compile time. > There is no compile-time only benefit of Thi...
2017 Jul 13
2
Question about thinLTO
On Thu, Jul 13, 2017 at 2:54 AM, Christudasan D <xander.cd at gmail.com> wrote: > Thank you Teresa. > > Yes, I would like to save the IR (*.bc and/or *.ll) after all > optimizations (especially thinLTO) are done and call *llc* separately. > Is there any specific document available online to see more about this > featur...
2020 Jul 26
2
[LAA] RtCheck on pointers of different address spaces.
..."LAA: Runtime check would require comparison between" " different address spaces\n"); return false; } Regards, CD From: Stefanos Baziotis <stefanos.baziotis at gmail.com> Sent: Sunday, July 26, 2020 6:09 PM To: Devadasan, Christudasan <Christudasan.Devadasan at amd.com> Cc: LLVM Dev <llvm-dev at lists.llvm.org> Subject: Re: [llvm-dev] [LAA] RtCheck on pointers of different address spaces. [CAUTION: External Email] Hi, There are a lot of things going on here, but given this: > The crash occurs with the pointers...
2017 Jul 12
2
Question about thinLTO
On Wed, Jul 12, 2017 at 10:19 AM, Teresa Johnson <tejohnson at google.com> wrote: > Hi Christu, > > Thanks for the note! > > On Wed, Jul 12, 2017 at 9:56 AM, Christudasan D via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> Hello, >> >> >> >> My impression on *thinLTO* when I first heard of it, (EuroLLVM2015) was >> about achieving Cross Module Optimization (CMO) at the IR level. >> >> >> >&g...
2017 Jul 12
2
Question about thinLTO
Hello, My impression on *thinLTO* when I first heard of it, (EuroLLVM2015) was about achieving Cross Module Optimization (CMO) at the IR level. Having parallel front-end compilation & initial optimization first, a thin-link of individual input units, more optimization by calling opt again on the combined IR, and finally the target codegen using llc. A transformation similar to the
2020 Jul 26
2
[LAA] RtCheck on pointers of different address spaces.
Hello, I Have a question related to the RT check on pointers during Loop Access Analysis pass. There is a testcase with loop code that consist of 4 different memory operations referring two global objects of different address spaces. One from global constant (address space 4, addr_size = 64) and the other from local, LDS (address space 3, addr_size= 32). (Details of various address spaces