search for: manilov

On Wed, May 4, 2016 at 3:10 PM, Stanislav Manilov < stanislav.manilov at gmail.com> wrote: > As in "look at the source of clang" or as in "look at the -S -emit-llvm" > output? If you mean the former, then would that be easy for someone who > hasn't seen the clang source before? > Generally the latter - th...

...Stan On Wed, Jun 21, 2017 at 7:21 PM, Philip Pfaffe <philip.pfaffe at gmail.com> wrote: > Hi Stan, > > can you share your example.bc? Can you reproduce your issue with llvm 4.0 > or, better even, trunk? > > Cheers, > Philip > > 2017-06-21 18:58 GMT+02:00 Stanislav Manilov <stanislav.manilov at gmail.com> > : > >> Hi Philip, >> >> Thanks for checking! >> >> I'm running my own Foo pass that registers DependenceAnalysisWrapperPass >> as a prerequisite and then I run it like so: >> >> opt -load libfoo.so -f...

Oh, I see, that makes a lot of sense. How do I build the pass pipeline? On Thu, Feb 11, 2016 at 5:54 PM, Mehdi Amini <mehdi.amini at apple.com> wrote: > > On Feb 11, 2016, at 9:49 AM, Stanislav Manilov via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > > > Hello, > > > > I am used to specifying dependence on other LLVM passes in the > `getAnalysisUsage(AnalysisUsage &)` method of my pass. However, it doesn't > seem that there is a header file th...

...5:40 PM, Philip Pfaffe <philip.pfaffe at gmail.com> wrote: > Hi Stan, > > in both cases I get a consistent anti result. Can you show us the command > lines you're using? Which version of llvm is this? > > Best, > Philip > > 2017-06-21 17:56 GMT+02:00 Stanislav Manilov via llvm-dev < > llvm-dev at lists.llvm.org>: > >> Hello llvm-dev, >> >> I'm running a pass that uses the result of llvm::DependenceAnalysisWrapperPass >> to compute the dependencies between all instructions of a loop. I have the >> following two exampl...

The usual advice I provide people is "see what Clang does with an equivalent C construct" On Wed, May 4, 2016 at 12:18 PM, Stanislav Manilov < stanislav.manilov at gmail.com> wrote: > Hi, > > There is another benefit to keeping the CppBackend: it's great for > learning how to use the IR and the C++ API in particular, as can be seen > from this SO Q&A: > http://stackoverflow.com/questions/16656855/llvm-ir...

On 26 September 2013 17:52, Stanislav Manilov <stanislav.manilov at gmail.com>wrote: > To answer your question I am testing on a pandaboard currently, which has > an arm cortex-a9 processor, which I think is 64-bit. > Cortex-A9 is still 32-bits, so you'll have all support you need. ;) however it doesn't if I remove t...

...eestanding -O3 -S -o - neon.c however it doesn't if I remove the -ffreestanding flag. I need to figure this out next. Thank you for your help. Cheers, - Stan On Thu, Sep 26, 2013 at 4:01 PM, Renato Golin <renato.golin at linaro.org>wrote: > On 26 September 2013 12:22, Stanislav Manilov <S.Z.Manilov at sms.ed.ac.uk>wrote: > >> In the process I found out that clang doesn't support NEON (as per >> http://blog.llvm.org/2010/04/arm-advanced-simd-neon-intrinsics-and.html), >> but there has been at least some effort in adding it ( >> https://www.cod...

...plement the intrinsics in clang itself (not sure this is the best way of doing it). Ideally, I want to be able to compile C code that includes ARM NEON intrinsics to other targets (TI processors, e.g.). Suggestions, comments, and recommendations are very welcome. Kind regards, - Stan -- Stan Manilov 1st year Ph.D. student 2013 Graduate in B.Sc. Computer Science and Mathematics The University of Edinburgh -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130926/b31b3f2b/attachment.html>

On 26 September 2013 18:13, Stanislav Manilov <stanislav.manilov at gmail.com>wrote: > which I suspect has something to do with the fact that in /usr/include I > have a folder called x86_64-linux-gnu but not one > called arm-linux-gnueabihf. Am I even remotely right? > Yes, you are, and the docs should (hopefully) have all...

> To answer your question I am testing on a pandaboard currently, which has >> an arm cortex-a9 processor, which I think is 64-bit. >> > > Cortex-A9 is still 32-bits, so you'll have all support you need. ;) > Ah, Okay, embarrassing... however it doesn't if I remove the -ffreestanding flag. I need to figure >> this out next. >> > > Can you at

Hello, I am used to specifying dependence on other LLVM passes in the `getAnalysisUsage(AnalysisUsage &)` method of my pass. However, it doesn't seem that there is a header file that exposes the `mem2reg` pass - it is implemented in `Mem2Reg.cpp` as a wrapper. Is there an easy way to reuse this pass, or should I, in essence, duplicate `Mem2Reg.cpp` in my project? Cheers, - Stan

On 2 October 2013 12:34, Stanislav Manilov <stanislav.manilov at gmail.com>wrote: > Again, the tool you describe is exactly what I ultimately want to create. > The translation to AltiVec would be a step towards understanding how to > manipulate the intrinsics, but it is not a goal on its own. > > Do you have any ideas...

Hello, I was trying to compile a simple program with the CppBackend like so: $ clang str_arg.c -emit-llvm -S $ llc -march=cpp str_arg.ll It produces a file `str_arg.cpp` as expected, however it doesn't seem that the resulting file is correct. For once, it includes `<llvm/Analysis/Verifier.h>` which seems to have been moved to `llvm/IR/Verifier.h` as far back as 2013. My question is

Hello llvm-dev, I'm running a pass that uses the result of llvm::DependenceAnalysisWrapperPass to compute the dependencies between all instructions of a loop. I have the following two examples of code I wish to analyse: example A: ``` void move_one(int *A, unsigned n) { for (unsigned i = 0; i < n-1; ++i) { A[i] = A[i + 1]; } } ``` and example B: ``` void move_one_alt(int *A,

Hello Hal, I am not very familiar with the DSP capabilities of PowerPC, but I imagine there will be instructions for simple vector operations like vector addition, multiplication, etc. so for these I imagine the implementation would consist of just outputting the correct instruction. However, for NEON instructions like the reciprocal step (see

...ly isn't IMO) -- someone also pointed out that it also really ought to be using IRBuilder...if anyone cared about it. On Tue, May 3, 2016 at 4:14 PM, Sean Silva via llvm-dev < llvm-dev at lists.llvm.org> wrote: > AFAICT it is dead. > > On Tue, May 3, 2016 at 4:04 AM, Stanislav Manilov via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> Hello, >> >> I was trying to compile a simple program with the CppBackend like so: >> >> $ clang str_arg.c -emit-llvm -S >> $ llc -march=cpp str_arg.ll >> >> It produces a file `str_...

Hello LLVM Devs, Thanks for helping me previously to cross-compile for ARM, I managed to get a working toolchain and am currently having fun compiling different toy problems and running them on a pandaboard. As part of my research I am trying to implement the ARM NEON Intrinsics in the PowerPC LLVM backend. I am still at the beginning of my efforts and am not yet familiar with either the ARM or

+1 On Wed, May 4, 2016 at 3:10 AM, Filipe Cabecinhas via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi, > > On Wed, May 4, 2016 at 9:35 AM, Ronan KERYELL via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > >>>>>> On Tue, 3 May 2016 16:36:01 -0400, Rafael Espíndola via llvm-dev < > llvm-dev at lists.llvm.org> said: > > > >

On 2 October 2013 12:17, Renato Golin <renato.golin at linaro.org> wrote: > On 2 October 2013 10:12, Steven Newbury <steve at snewbury.org.uk> wrote: > >> How does this make any sense? >> > > I have to agree with you that this doesn't make much sense, but there is a > case where you would want something like that: when the original source > uses NEON

...to be using IRBuilder...if anyone cared about it. > > > On Tue, May 3, 2016 at 4:14 PM, Sean Silva via llvm-dev > <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: > > AFAICT it is dead. > > On Tue, May 3, 2016 at 4:04 AM, Stanislav Manilov via llvm-dev > <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: > > Hello, > > I was trying to compile a simple program with the CppBackend > like so: > > $ clang str_arg.c -emit-llvm -S > $ ll...