similar to: [LLVMdev] GCC 3.4.1 and conflicting types for 'malloc'

Displaying 20 results from an estimated 5000 matches similar to: "[LLVMdev] GCC 3.4.1 and conflicting types for 'malloc'"

2005 Mar 12
1
[LLVMdev] GCC 3.4.1 and conflicting types for 'malloc' (2)
It seems that this happened before but I do not know the details: http://llvm.cs.uiuc.edu/testresults/SparcV9/2004-12-07.html Thanks --- Chris Lattner <sabre at nondot.org> wrote: > On Sat, 12 Mar 2005, xavier wrote: > > llvm[2]: Compiling zalloc.c for Release build > > /homes/myuser/LLVM/llvmobj/../llvmsrc/utils/Burg/zalloc.c:9: error: conflictin > > g types for
2005 Mar 12
1
[LLVMdev] GCC 3.4.1 and conflicting types for 'malloc' (2)
I commented this line and it is compiling now: extern void *malloc ARGS((unsigned)); I hope that will not cause a different kind of problem. What it is zalloc used for? Thanks --- Chris Lattner <sabre at nondot.org> wrote: > On Sat, 12 Mar 2005, xavier wrote: > > > It seems that this happened before but I do not know the details: > >
2005 Mar 12
0
[LLVMdev] GCC 3.4.1 and conflicting types for 'malloc'
Chris, Thanks for your answer Here is the verbose output: =========================== gmake tools-only VERBOSE=1 TOOL_VERBOSE=1 for dir in lib/System lib/Support utils lib tools ; do \ if [ ! -f $dir/Makefile ]; then \ /home/myuser/LLVM/objdir/../srcdir/autoconf/mkinstalldirs $dir; \ cp /home/myuser/LLVM/objdir/../srcdir//$dir/Makefile $dir/Makefile; \ fi; \ (gmake -C $dir all )
2005 Mar 12
2
[LLVMdev] GCC 3.4.1 and conflicting types for 'malloc' (2)
Yes, sorry for not mentioning it. I added that header also Although I suppose that if I am not using Sparc there will be no problem (it's an Itanium 2 machine) Thanks --- Chris Lattner <sabre at nondot.org> wrote: > On Sat, 12 Mar 2005, xavier wrote: > > > I commented this line and it is compiling now: > > > > extern void *malloc ARGS((unsigned)); > >
2008 Apr 04
2
[LLVMdev] PATCH: Use size reduction -- wave1
heisenbug wrote: > On Apr 3, 10:53 pm, Gabor Greif <ga... at mac.com> wrote: > ... > > >>> 3) Make sure that make check and some reasonable subset of llvm-test >>> passes with this patch :) >>> >> I have never run llvm-test in the past. Is it just checking it out and >> following a readme? >> > > > After
2005 Mar 12
1
[LLVMdev] GCC 3.4.1 and conflicting types for 'malloc'
Hi I am trying to build the llvm tools following the instructions here: http://llvm.cs.uiuc.edu/docs/CFEBuildInstrs.html But I get this error: /zalloc.c:9: error: conflicting types for 'malloc' I am using gcc 3.4.1 What can be the problem? __________________________________ Do you Yahoo!? Yahoo! Sports - Sign up for Fantasy Baseball. http://baseball.fantasysports.yahoo.com/
2008 Apr 04
0
[LLVMdev] PATCH: Use size reduction -- wave1
On Apr 4, 7:51 pm, Török Edwin <edwinto... at gmail.com> wrote: > heisenbug wrote: > > On Apr 3, 10:53 pm, Gabor Greif <ga... at mac.com> wrote: > > ... > > >>> 3) Make sure that make check and some reasonable subset of llvm-test > >>> passes with this patch :) > > >> I have never run llvm-test in the past. Is it just checking it
2009 Feb 05
0
[LLVMdev] make TEST=dbgopt donesn't work?
> > Are you able to run nightly test ? > Yes, I can run nightly test. > Here is what I see... > > $ make TEST=dbgopt > /Developer/usr/bin//llvm-gcc sse.expandfft.c -g --emit-llvm -c -o > Output/sse.expandfft.bc > /Volumes/Nanpura/mainline/llvm/Debug/bin/opt Output/sse.expandfft.bc - > strip-nondebug -strip-debug -std-compile-opts -strip -f -o Output/ >
2007 Sep 30
3
[LLVMdev] Compiling poolalloc
I currently have a slightly modified llvm-2.0 source tree (from the release tarball). I checked out poolalloc into the projects directory and attempt to configure it, but I keep getting errors. I would understand if there were problems building it (since it may require a different version of llvm), but it should at least configure. Specifically, I've tried the following commands: >
2005 Apr 22
0
[LLVMdev] tabs
I found 179 more *.{c,cpp,h} files with tabs. Unfortunately, the tabs stops used vary so blindly expanding them messes up alignment in many cases :( Index: examples/BFtoLLVM/BFtoLLVM.cpp Index: include/llvm/AbstractTypeUser.h Index: include/llvm/GlobalVariable.h Index: include/llvm/InstrTypes.h Index: include/llvm/IntrinsicInst.h Index: include/llvm/ADT/PostOrderIterator.h Index:
2007 Sep 30
0
[LLVMdev] Compiling poolalloc
On Sunday 30 September 2007, Ben Chambers wrote: > Specifically, I've tried the following commands: > > ./configure --with-llvmsrc=~/Documents/research/llvm/llvm-2.0/ > > --with-llvmobj=~/Documents/research/llvm/llvm-2.0/Release/bin/ > > > > ./configure --with-llvmsrc=~/Documents/research/llvm/llvm-2.0/ > >
2008 Apr 04
3
[LLVMdev] PATCH: Use size reduction -- wave1
On Apr 4, 8:06 pm, heisenbug <ggr... at gmail.com> wrote: > On Apr 4, 7:51 pm, Török Edwin <edwinto... at gmail.com> wrote: > > > > > heisenbug wrote: > > > On Apr 3, 10:53 pm, Gabor Greif <ga... at mac.com> wrote: > > > ... > > > >>> 3) Make sure that make check and some reasonable subset of llvm-test > > >>>
2008 Apr 11
4
[LLVMdev] Setting up new project
Hi, I am attempting to set up a new frontend project based on the sample project (I'm following the instructions at http://llvm.org/docs/Projects.html). In doing so, I hit a problem with AutoRegen.sh which I worked around, and hit a problem with configure that I don't know how to work around. Below is what happens when I attempt to autoconf and configure the sample project that ships
2003 Aug 21
0
[LLVMdev] reoptimizer note
Hello, In preparation for the LLVM public release, I've moved the reoptimizer out of the main cvs module "llvm" and into the cvs module "reopt". You can go ahead and delete the lib/Reoptimizer directory from your tree, about which cvs will undoubtedly be complaining to you. If you want to build the reoptimizer, cd into your SPARC tree's "projects"
2008 Apr 13
0
[LLVMdev] Setting up new project
On Sat, Apr 12, 2008 at 3:52 PM, Criswell, John T <criswell at ad.uiuc.edu> wrote: > Try using the --with-llvmsrc and --with-llvmobj options to explicitly set the locations of your LLVM source tree and object tree, respectively. I faintly recall seeing this error and seem to recall using these options to work around it. OK. Here are the complete steps required to successfully build the
2008 Apr 11
0
[LLVMdev] Setting up new project
On Fri, Apr 11, 2008 at 9:39 AM, Lane Schwartz <dowobeha at gmail.com> wrote: > Hi, > > I am attempting to set up a new frontend project based on the sample > project (I'm following the instructions at > http://llvm.org/docs/Projects.html). In doing so, I hit a problem with > AutoRegen.sh which I worked around, and hit a problem with configure > that I don't
2008 Apr 12
3
[LLVMdev] Setting up new project
Try using the --with-llvmsrc and --with-llvmobj options to explicitly set the locations of your LLVM source tree and object tree, respectively. I faintly recall seeing this error and seem to recall using these options to work around it. -- John T. ________________________________________ From: llvmdev-bounces at cs.uiuc.edu [llvmdev-bounces at cs.uiuc.edu] On Behalf Of Lane Schwartz [dowobeha at
2009 Feb 23
3
[LLVMdev] how to build llvm-test in separate directory
On Mon, Feb 23, 2009 at 6:32 PM, John Criswell <criswell at cs.uiuc.edu> wrote: > Aaron Gray wrote: > > I am trying to build llvm-test in a separate directory to the main llvm > tree. > > > > I have put llvm and llvm-gcc's bin directories on the path but think I am > missing a switch on the configure command. > > > You need to use --with-llvmsrc and
2010 Jun 29
1
[LLVMdev] problems building vmkit
Hi All, Thanks Nicolas for pointing out that I needed --enable-targets=x86,cpp for my llvm config to get vmkit to build. The process gets a lot farther but fails in different places depending upon the vmkit config (Can you please see the three case below?). My machine is a intel core i7 running ubuntu karmic and gcc 4.4.1. What arch/OS/distro/gcc do you all have VMKit working on? thanks for
2013 Nov 26
2
syslinux.efi pxeboot across multiple subnets
On 11/24/2013 03:29 AM, Gene Cumm wrote: >> >> (Sorry for the top posting.) > > I just started examining this and find it odd that the core_udp_recv() > doesn't zalloc() its token while core_udp_send()/core_udp_sendto() do. > All three are a part of commit fe283b78 by Matt Fleming. Should this > be made into a zalloc() rather than pushing it into the stack?