search for: path_to_librari

Displaying 5 results from an estimated 5 matches for "path_to_librari".

Did you mean: path_to_library
2015 Jul 02
2
[LLVMdev] Load MachineFunctionPass plugin from library in llc?
Hi all, I am working on creating a MachineFunctionPass to perform an analysis on X86 code. After a bit of trouble, I was able to get my pass compiling and running correctly in llc. However, since a machine pass is compiled directly into the code generator, rerunning "make" across the LLVM build tree involves re-linking most of the major libraries and executables. This is a rather
2015 Jul 02
2
[LLVMdev] Load MachineFunctionPass plugin from library in llc?
> On Jul 2, 2015, at 2:05 PM, Jim Grosbach <grosbach at apple.com> wrote: > >> >> On Jul 2, 2015, at 1:17 PM, Ethan J. Johnson <ejohns48 at cs.rochester.edu <mailto:ejohns48 at cs.rochester.edu>> wrote: >> >> Hi all, >> >> I am working on creating a MachineFunctionPass to perform an analysis on X86 code. After a bit of trouble, I was
2020 Sep 30
2
OrcV1 removal
Hi, On 2020-09-29 13:58:35 -0700, Lang Hames wrote: > > Have the basics working. Should I open a PR to your branch for what I > > got so far? > Sounds good to me. Done, https://github.com/lhames/llvm-project/pull/2 . > The first is to expose more of symbol resolution. Postgres can be > > extended via dynamically loaded libraries, and we need to be careful to > >
2012 Nov 16
0
[LLVMdev] Using custom LLVM Passes with clang
Hello, I have written a custom LLVM Loop Pass that perforates a loop by changing the increment value for the induction variable. I am able to run this pass using the opt command and loading the shared object library from Debug+Asserts as detailed in http://llvm.org/docs/WritingAnLLVMPass.html I was wondering if this pass can be used in clang somehow. I have read about "-mllvm"
2020 Sep 29
3
OrcV1 removal
Hi, On 2020-09-25 16:38:41 -0700, Andres Freund via llvm-dev wrote: > On 2020-09-24 16:34:30 -0700, Lang Hames wrote: > > If anyone wants to check out the OrcV1 removal branch and provide feedback > > now is the time. Otherwise I will aim to land the work in the mainline > > early next week. > > I'm trying to get it to work with postgres. Unfortunately this week