search for: bandhav

...body.preheader, label %for.cond.cleanup . . ... I'm running this with LLVM RISC-V backend using RISC-V GCC compiled Newlib as the C/C++ library. Is it not okay to use GCC libraries with LLVM? Or could this be a specific issue with Newlib's header files misinterpreted by Clang? Thank you, Bandhav -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200628/1471034e/attachment-0001.html>

...s: is there a way to compile lines 23-26 assuming no aliasing between A and B, by just doing something in the RemotePtr class (so that main is clear of ugly code)? If that's not possible, is there a way to tell Clang that lines 23-26 should assume no aliasing at all, by some pragma? Thank you, Bandhav -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200621/7971fe25/attachment.html>

...Would this work for automatic variables as well? In regards to using this in the backend, do I have to just modify the source, or is it possible to load a library at runtime, like we load a frontend pass? On Tue, May 26, 2020 at 12:37 PM Henrik Olsson <hnrklssn at gmail.com> wrote: > Hi Bandhav, > > While I'm unfamiliar with the details of codegen and cost modelling in > LLVM, it is possible to declare multiple address spaces for a target, mark > pointers as belonging to a specific address space, and cast between them. > To quote the language reference "For targets...

...from address > 0x80000000, take 10-100 cycles. Is it possible to model these costs in the scheduler? Requiring programmer to define custom pointer types to mark pointers, to one or the other address space, is okay. Is there a way to model different costs for different pointer types? Thank you, Bandhav -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200525/264336ae/attachment.html>

...ec_add and main should be the same right? Is there anything else I should do to make the __restrict remove loop-carried dependence in main? Attaching IR and scheduler log for reference... On Mon, Jun 22, 2020 at 3:03 PM Jeroen Dobbelaere < Jeroen.Dobbelaere at synopsys.com> wrote: > Hi Bandhav, > > > > as mentioned in the summary of https://reviews.llvm.org/D69542 : > > > > The base version is b2a37cfe2bda0bc8c4d2e981922b5ac59c429bdc > <https://reviews.llvm.org/rGb2a37cfe2bda0bc8c4d2e981922b5ac59c429bdc> > (June 12, 2020) > > > > Greeti...

...known to now handle noalias metadata correctly as it just copies it. There has been a discussion here: http://lists.llvm.org/pipermail/llvm-dev/2020-May/141587.html Michael Am So., 21. Juni 2020 um 12:24 Uhr schrieb Johannes Doerfert via llvm-dev <llvm-dev at lists.llvm.org>: > > Hi Bandhav, > > > Jeroen Dobbelaere (CC'ed) is currently working on support for restrict qualified local variables and struct members. > > The patches exist but are not merged yet. If you want to give it a try apply https://reviews.llvm.org/D69542. > > > Initially I could only thin...

...roen, That's great! I was trying to use the patch, what's the latest version of the project we could apply it on? Hi Neil, That seems like what I can do as well! Do you happen to have some examples lying around? Maybe a pointer to the planned presentation, if that's okay? Thank you, Bandhav On Mon, Jun 22, 2020 at 1:55 AM Neil Henning <neil.henning at unity3d.com> wrote: > I was originally going to cover this in my now defunct EuroLLVM talk > but... we had this exact same problem on Unity's HPC# Burst compiler - how > to track no-aliasing on structs. We were const...