similar to: [LLVMdev] [PATCH] AutoRegen.sh in poolalloc branch

Displaying 20 results from an estimated 10000 matches similar to: "[LLVMdev] [PATCH] AutoRegen.sh in poolalloc branch"

2008 May 07
0
[LLVMdev] Path to AutoRegen.sh
> * I'm using Autoconf 2.61, and it is compatible with the syntax used > by LLVM, but AutoRegen.sh insists I need 2.5x. > > * There is a bug in the AutoRegen.sh that appears when you try to > regenerate configure scripts for your project outside the LLVM > source tree: an shell "read" command missing a parameter. > > The patch was tested on 2.2, but I think
2008 May 07
4
[LLVMdev] Path to AutoRegen.sh
Hello, people I'm developing a small code analysis project with LLVM (I hope I can concentrate on it next semester and make it a really functional tool, but, for now, it's an college end course project, and I'm more focused on theoretical issues than on the implementation). I'm using Ubuntu Linux and had a lot of trouble starting the project by copping the "sample
2007 Feb 13
2
[LLVMdev] using dsa from llvm-poolalloc
I have a few questions on using dsa now that it has been moved out of llvm. I have llvm -r release_19 checked out from cvs, and llvm-poolalloc -r release_19 checked out from cvs into the projects directory, as John Criswell previously suggested. 1) I have some compiler transforms that I'm writing that use DSA. They can no longer find the header files for DSA. My transforms are located
2007 Feb 13
0
[LLVMdev] using dsa from llvm-poolalloc
Ryan M. Lefever wrote: > I have a few questions on using dsa now that it has been moved out of > llvm. I have llvm -r release_19 checked out from cvs, and > llvm-poolalloc -r release_19 checked out from cvs into the projects > directory, as John Criswell previously suggested. > > 1) I have some compiler transforms that I'm writing that use DSA. They > can no longer
2008 May 07
1
[LLVMdev] Path to AutoRegen.sh
Hy, Tanya > Some comments: > - Please follow the developers policy for making patches: > http://llvm.org/docs/DeveloperPolicy.html#patches > OK. My fault here. Will check some of your observations and resubmit. > - I think if we are going to upgrade, we should totally switch to 2.6 > instead of allowing both. This will make diffs easier to read when people > regenerate
2010 Dec 26
2
[LLVMdev] Question of executing AutoRegen.sh to regen configure file
Hello all, I download the src of llvm 2.8 and run ./autoconf/AutoRegen.sh However there is a little difference between origin configure file and the generated one $diff configure configure.bak 1394c1394 < --enable-optimized Compile with optimizations enabled (default is YES) --- > --enable-optimized Compile with optimizations enabled (default is NO) I am wondering to know
2011 Jan 03
0
[LLVMdev] Question of executing AutoRegen.sh to regen configure file
On Dec 26, 2010, at 8:38 AM, Lu Mitnick wrote: > Hello all, > > I download the src of llvm 2.8 and run ./autoconf/AutoRegen.sh > > However there is a little difference between origin configure file and the generated one > > $diff configure configure.bak > > 1394c1394 > < --enable-optimized Compile with optimizations enabled (default is YES) > ---
2008 May 07
0
[LLVMdev] Path to AutoRegen.sh
Hi, I think I have quite an identical patch lying around somewhere here, but I thought that the AutoRegen.sh was something someone wrote here in-house, so I never bothered to send it somewhere. I do remember someone saying (on this list) one should really not use another version of autoconf, but in my experience 2.6 works just as fine for building an addon project (but perhaps not for rebuilding
2008 May 07
1
[LLVMdev] Path to AutoRegen.sh
Hi, Matthijs Tanya addressed some of these issues on her response to my patch. You can see there some comments. Thanks about the ubuntu 'dash' issue. Never minded which shell I was using here... it's very like bash from user viewpoint. I think it's another reason to have the variable on the command line. Alexandre Em Qua, 2008-05-07 às 18:26 +0200, Matthijs Kooijman escreveu:
2011 Jan 03
2
[LLVMdev] Question of executing AutoRegen.sh to regen configure file
On Mon, Jan 3, 2011 at 11:01 AM, Eric Christopher <echristo at apple.com> wrote: > On Dec 26, 2010, at 8:38 AM, Lu Mitnick wrote: >> $diff configure configure.bak >> >> 1394c1394 >> <   --enable-optimized      Compile with optimizations enabled (default is YES) >> --- >> >   --enable-optimized      Compile with optimizations enabled (default is
2015 May 28
0
[LLVMdev] Building poolalloc with current LLVM development branch?
I'm pretty sure poolalloc is unmaintained at this point. John Criswell would know more. On Thu, May 28, 2015 at 11:57 AM, Christian Convey < christian.convey at gmail.com> wrote: > I'm starting to play around with poolalloc for the first time. I tried to > build it as follows: > 1) Clone llvm's git repo, and build it with cmake + ninja. > 2) cd .../llvm/projects
2015 May 30
1
[LLVMdev] Building poolalloc with current LLVM development branch?
Hi Will, John Criswell thought that perhaps you've gotten DSA (but not poolalloc) working with the mainline LLVM code. If that's true, is that something you intend to share? I for one would love to be able to use it. - Christian On Sat, May 30, 2015 at 12:06 PM, John Criswell <jtcriswel at gmail.com> wrote: > Dear Christian, > > First, I've never used CMake to
2011 Apr 04
0
[LLVMdev] Problem building the LLVM sample project
On 4/4/11 9:25 AM, Pablo Barrio wrote: > Hi all, > > I'm starting a new project and I'm having some trouble with the LLVM > configure+Makefile system. > > When I type "./configure" in the sample project, it seems to work. > However, after going down to the autoconf dir and typing > "./AutoRegen.sh", when I go back to the project main dir and type
2008 Apr 11
0
[LLVMdev] Setting up new project
Lane Schwartz wrote: > [snip] > OK then. I didn't realize that having a newer version would be a problem. > > I compiled and installed autoconf 2.59. I still get the same problem: > > $ autoconf --version > autoconf (GNU Autoconf) 2.59 > > $ cd /opt/src-llvm/projects/sample/autoconf > $ ./AutoRegen.sh > $ cd .. > > $ ./configure
2015 May 30
0
[LLVMdev] Building poolalloc with current LLVM development branch?
Dear Christian, First, I've never used CMake to build poolalloc. I've always used the autoconf-based build system. It is possible that the CMake files for poolalloc are broken. I recommend using the autoconf-based build system. Second, you'll be pleased to know that someone (I think Will Dietz) has gotten DSA working with mainline LLVM. The DSA code compiles, but not the
2010 Mar 10
1
[LLVMdev] SAFECode and Poolalloc Branches for LLVM 2.6
Please create a similar branch for Klee; I've been working on porting that to 2.7 as well.<br /> <br /> Best, Erich Ocean<br /> <br /> On Fri, Mar 5, 2010 at 8:43 PM, John Criswell (criswell@uiuc.edu) wrote:<br /> > <br /> > Dear SAFECoders and LLVMers,<br /> > <br /> > There is some new work on moving DSA to the new LLVM 2.7 API.
2010 Mar 05
0
[LLVMdev] SAFECode and Poolalloc Branches for LLVM 2.6
Dear SAFECoders and LLVMers, There is some new work on moving DSA to the new LLVM 2.7 API. I am hoping to do something similar for SAFECode once the code freeze occurs. To keep things running smoothly, there are now release_26 branches for the poolalloc and safecode projects. If you are using SAFECode, Poolalloc, or DSA with LLVM 2.6, you will want to switch to these branches. To get
2015 May 28
5
[LLVMdev] Building poolalloc with current LLVM development branch?
I'm starting to play around with poolalloc for the first time. I tried to build it as follows: 1) Clone llvm's git repo, and build it with cmake + ninja. 2) cd .../llvm/projects 3) git clone git at github.com:llvm-mirror/poolalloc.git When I went to re-run ninja, (or even CMake by itself), I get errors like the following (truncated for brevity). Any suggestions for whether I'm
2008 Dec 17
2
[LLVMdev] AutoRegen.sh bug
Hi, I am just starting a new project. I found that the above script rejects Autoconf versions later than 2.59, whereas it ought to accept them, imho. I had to edit the scrip to be able to use it with Autoconf 2.61. Also, aclocal gave the following warning: /usr/share/aclocal/oaf.m4:4: warning: underquoted definition of AM_PATH_OAF /usr/share/aclocal/oaf.m4:4: run info '(automake)Extending
2008 Apr 12
2
[LLVMdev] Setting up new project
On Fri, Apr 11, 2008 at 3:24 PM, John Criswell <criswell at cs.uiuc.edu> wrote: > Lane Schwartz wrote: > > > [snip] > > > > OK then. I didn't realize that having a newer version would be a problem. > > > > I compiled and installed autoconf 2.59. I still get the same problem: > > > > $ autoconf --version > > autoconf (GNU Autoconf)