search for: fifield

Displaying 17 results from an estimated 17 matches for "fifield".

2013 Feb 08
3
[LLVMdev] The MBlaze backend: can we remove it?
Hi, I just saw this thread. I work on llvm at Xilinx but I do not work on microblaze. I will check to see if there is any interest here at Xilinx to contribute resources to the maintenance of this backend. Thanks, Jeff On Tue, Feb 5, 2013 at 7:38 PM, Rogelio Serrano <rogelio.serrano at gmail.com>wrote: > > On Feb 6, 2013 4:52 AM, "Chandler Carruth" <chandlerc at
2013 Feb 28
0
[LLVMdev] The MBlaze backend: can we remove it?
Hi jeff! Any news? On Feb 9, 2013 1:53 AM, "Jeff Fifield" <fifield at mtnhigh.net> wrote: > Hi, > > I just saw this thread. I work on llvm at Xilinx but I do not work on > microblaze. > > I will check to see if there is any interest here at Xilinx to contribute > resources to the maintenance of this backend. > > Th...
2011 Nov 16
2
[LLVMdev] Dev Meeting: Volunteer Moderators Needed!
...35-3:05): Using Clang in the Chromium project: Nico Weber, Hans Wennborg – Google Android Renderscript: Stephen Hines – Google Session #4 (1:35-3:05): Polly - First successful optimizations —How to Proceed?: Tobias Grosser – ENS/INRIA SKIR: Just-in-Time Compilation for Parrallelism with LLVM: Jeff Fifield – University of Colorado Session #5: (3:45-6:00): Exporting 3D scenes from Maya to WebGL using clang and LLVM: Jochen Wilhelmv – Consultant Finding races and memory errors with LLVM instrumentation: Konstantin Serebrvanv – Google Backend/Infrastructure Super BoF: Jim Grosbach – Apple A moderator...
1999 Jan 18
0
[Fwd: [SECURITY] ftpwatch package has major security problems]
-------- Original Message -------- Subject: [SECURITY] ftpwatch package has major security problems Date: Sun, 17 Jan 1999 11:48:22 -0400 From: Jamie Fifield <fifield@CS.DAL.CA> Reply-To: security@debian.org -----BEGIN PGP SIGNED MESSAGE----- We have found that the ftpwatch package as distributed in Debian GNU/Linux 1.3 and later distributions has a security problem which makes it trivial for users to gain root access. We recommend that you rem...
2013 Jul 24
0
[LLVMdev] Deprecating and removing the MBlaze backend
Chandler brought up removing it back in February but Rogelio Serrano said he could maintain it and Jeff Fifield from Xilinx was supposed to check if someone could help. If no one has stepped up in the past 5 months, then I don't see an issue with removing it. Micah > -----Original Message----- > From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] > On Behalf Of Eric C...
2011 Sep 03
0
[LLVMdev] LLVM: Cannot instantiate JIT execution engine
I see two problems in your code 1) you need to #include "llvm/ExecutionEngine/JIT.h" 2) you must pass an empty string to EngineBuilder::setErrorStr. See JIT::createJIT for the reason. Jeff On Sat, Sep 3, 2011 at 8:33 AM, Semion Prihodko <semion.ababo at gmail.com> wrote: > Isn't there someone to help me with this issue? I'm very upset about this > stupid problem
2013 Jul 24
5
[LLVMdev] Deprecating and removing the MBlaze backend
Doesn't seem to get a lot of love since most of the commits in the last 3 years have been maintenance. I guess it doesn't take a whole lot of maintenance either, but... cc'ing Wesley since he seems to be the last guy to commit to it. Thoughts? -eric
2011 Sep 03
1
[LLVMdev] LLVM: Cannot instantiate JIT execution engine
Isn't there someone to help me with this issue? I'm very upset about this stupid problem which wasted the whole day. BTW, I can create JIT from main.cpp, but not in the required source file (runtime.cpp), so this is not about linking. Very weird. 2011/9/2 Semion Prihodko <semion.ababo at gmail.com> > I cannot call the constructor explicitly, because ForceJITLinking is a name
2011 Oct 13
0
[LLVMdev] RFC/Heads Up: Deprecating External Build Support
...#39;s own build system (so that we are more free to make changes to how the project itself builds). However, I will plan on doing this by refactoring the existing test-suite and sample project to work that way, instead of removing them completely. - Daniel On Tue, Oct 11, 2011 at 11:42 PM, Jeff Fifield <fifield at colorado.edu> wrote: > On Tue, Oct 11, 2011 at 11:49 PM, Anna Zaks <ganna at apple.com> wrote: >> On Oct 11, 2011, at 3:02 PM, Daniel Dunbar wrote: >>> If the community thinks this is an important problem for LLVM to >>> address, then I think the i...
2011 Oct 10
0
[LLVMdev] A question about calling external function in JIT
...de library to your code before JIT (e.g. using llvm-link or llvm-ld), or you can essentially do the same thing manually in your code. This was discussed in a previous thread (http://bit.ly/oYbbsD). -Jeff > > Thanks a lots. > > Regards, > Wei-Fan > > 於 10/6/2011 1:45 PM, Jeff Fifield 提到: >> >> Hi Wei-Fan, >> >> It is possible to reference an external function from JITed code.  You >> can use the llvm::sys::DynamicLibrary routines to load your dynamic >> library.  After loading the library, the JIT engine should be able to >> locate '...
2011 Sep 02
0
[LLVMdev] Is it possible to inline Functions without using LLVM JIT Framework?
On Fri, Sep 2, 2011 at 4:23 AM, Mian M. Hamayun <mian-muhammad.hamayun at imag.fr> wrote: > But I am also looking into the possibility of doing the same using LLVM Pass > Manager (Without using llvm-ld). This looks difficult due to the fact that > the function definitions ought to be in the same module as the caller, in > order to be inlined and then optimized onwards, I guess
2011 Oct 06
2
[LLVMdev] A question about calling external function in JIT
Hello Sir, My name is Wei-Fan Chiang. I am now a graduated student of U. of Utah. I have a question about call external function in JIT. Suppose I have a simple program: int main (int argc, char *argv[]) { int i = 2, j = 3, k; k = foo(2, 3); return 0; } "foo" is an external function (non-native function define in dynamic library) made by us. In JIT, we just need to
2011 Oct 12
2
[LLVMdev] RFC/Heads Up: Deprecating External Build Support
On Tue, Oct 11, 2011 at 11:49 PM, Anna Zaks <ganna at apple.com> wrote: > On Oct 11, 2011, at 3:02 PM, Daniel Dunbar wrote: >> If the community thinks this is an important problem for LLVM to >> address, then I think the ideal solution is that we provide a set of >> autoconf/makefile/whatever foo that uses llvm-config and so on, but >> doesn't try and do things
2016 May 10
3
[OpenCL] Question about pre-linking passes required to build OpenCL program
+ llvm-dev From: Sumner, Brian Sent: Tuesday, May 10, 2016 3:11 PM To: Anastasia Stulova <Anastasia.Stulova at arm.com>; Liu, Yaxun (Sam) <Yaxun.Liu at amd.com>; cfe-dev (cfe-dev at lists.llvm.org) <cfe-dev at lists.llvm.org>; Pan, Xiuli <xiuli.pan at intel.com>; Bader, Alexey (alexey.bader at intel.com) <alexey.bader at intel.com> Cc: Stellard, Thomas
2011 Oct 06
0
[LLVMdev] MIPS 32bit code generation
...La Lama) 9. Re: svnsync of llvm tree (Oliver Schneider) 10. Re: svnsync of llvm tree (Oliver Schneider) 11. TR : LLVM and VHDL simulation (Baggett Jonas) 12. Re: TableGen and Greenspun (David A. Greene) 13. Re: svnsync of llvm tree (David A. Greene) 14. Re: svnsync of llvm tree (Jeff Fifield) 15. Re: LLVM and VHDL simulation (Jianzhou Zhao) 16. Re: TableGen and Greenspun (David A. Greene) 17. How to create arguments CallInst (Rafael Baldiati Parizi) 18. Re: How to create arguments CallInst (John Criswell) ----------------------------------------------------------------------...
2011 Sep 02
3
[LLVMdev] Is it possible to inline Functions without using LLVM JIT Framework?
Thanks Eric, Jim and Geovani for your responses. Yes, we can combine two or more bitcode modules using llvm-ld and in this way functions can be inlined and optimized during this process. But I am also looking into the possibility of doing the same using LLVM Pass Manager (Without using llvm-ld). This looks difficult due to the fact that the function definitions ought to be in the same module
2009 Mar 10
1
[LLVMdev] 2.5 Pre-release1 available for testing
Michel Salim wrote: > On Fri, Feb 6, 2009 at 8:42 PM, Tanya Lattner <tonic at nondot.org> wrote: >> LLVMers, >> >> The 2.5 pre-release is available for testing: >> http://llvm.org/prereleases/2.5/ >> > I'm updating the Fedora packaging of LLVM, and with the 02/20 > prerelease it fails to build on ppc64: > >