search for: llvm_home

Fixing one bug uncovers the next one... To reproduce: llvm-ar rc ./libgcc.a libgcc/./_muldi3.o <and-lots-more-.o-files...> The result: C:\msys\1.0\home\llvm_home\install\bin\llvm-ar.exe: Can't move './libgcc.a-000003' to './libgcc.a-000002': Cannot create a file when that file already exists. So apparently, we're trying to move one file on top of another. The error is generated in: Path::renamePathOnDisk(const Path& newName) {...

...oes not allow a file to be implicitly replaced via renaming. I'll fix it. Greg Pettyjohn wrote: > Fixing one bug uncovers the next one... > > To reproduce: > llvm-ar rc ./libgcc.a libgcc/./_muldi3.o <and-lots-more-.o-files...> > > The result: > C:\msys\1.0\home\llvm_home\install\bin\llvm-ar.exe: Can't move './libgcc.a-000003' to './libgcc.a-000002': Cannot create a file when that file already exists. > > So apparently, we're trying to move one file on top of another. > > The error is generated in: > > Path::renamePathOnDisk...

So the fundamental problem I'm trying to solve is how get my cfrontend build configured properly. The usual symptom of an incorrect configuration is the inability to find various header files. Here's some example spew: $ /home/llvm_home/llvm-gcc-build/gcc/xgcc -v -B/home/llvm_home/llvm-gcc-build/gcc/ -Bc:/msys/1.0/mingw32/bin/ -Bc:/msys/1.0/mingw32/lib/ -isystem c:/msys/1.0/mingw32/include -isystem c:/msys/1.0/mingw32/sys-include -O2 -I../../llvm-gcc/gcc/../winsup/w32api/include -DIN_GCC -DCROSS_COMPILE -DDEFAULT_TARGET_MACHINE=\&...

Hi, I have some questions about the compilation of the llvm. First, why the majority of the results of compilation are static library ( *.a files in the $(LLVM_HOME)/Release+Asserts/lib/), Why don't generate dynamic link library (.so files in the directory). The exception is the file libLTO.a and libLTO.so, why the library LTO were generated for static and dynamic both? How to control the generation of the library file, could it be controlled in the file M...

1. I got the tools to build. Yay! 2. I got past all the annoying trouble with not finding header files. Yay! Now I'm having problems with this: llvm-ar rc ./libgcc.a libgcc/./_muldi3.o <and-lots-more-.o-files...> C:\msys\1.0\home\llvm_home\install\bin\llvm-ar.exe: <invalid>: path is not valid I'm investigating this with the debugger and so far I've learned that '<invalid>' seems to be the default constructor for some kind of path object. I don't know why it's crapping out: 1. I expect it to *creat...

2008/12/28 Elvis Dowson <elvis.dowson at mac.com> > Where can I get gccas ? I am running Mac OS X 10.5.6 and I get the > following error: > gccas is one of the LLVM tools; you have to build them before building llvm-gcc and you should configure llvm-gcc with the --enable-llvm=[...] flag unless the LLVM tools are in your PATH. See

On Sat, 6 May 2006, Greg Pettyjohn wrote: > Now I'm having problems with this: > > llvm-ar rc ./libgcc.a libgcc/./_muldi3.o <and-lots-more-.o-files...> > C:\msys\1.0\home\llvm_home\install\bin\llvm-ar.exe: <invalid>: path is not valid > I've tracked this down in the debugger. It is indeed a bug. The problem is that Path::isValid() will reject a string containing "<" and ">" on Windows. Note that this is not the case on Unix -- compare...

Hello, Elvis > $ ../src/configure --program-prefix=llvm- --disable-bootstrap > --enable-checking --enable-languages=c,c++ You haven't configured llvm-gcc properly. Please do read readme.llvm file. However, afair, Trident was LLVM 1.5-based, and it will require massive rewrite to use LLVM 2.x (bytecode format was also changed) -- With best regards, Anton Korobeynikov Faculty of

...Reid. On Sat, 2006-05-06 at 16:43 -0400, Greg Pettyjohn wrote: > > On Sat, 6 May 2006, Greg Pettyjohn wrote: > > > Now I'm having problems with this: > > > > llvm-ar rc ./libgcc.a libgcc/./_muldi3.o <and-lots-more-.o-files...> > > C:\msys\1.0\home\llvm_home\install\bin\llvm-ar.exe: <invalid>: path is not valid > > > > I've tracked this down in the debugger. It is indeed a bug. The problem is > that Path::isValid() will reject a string containing "<" and ">" on > Windows. > > Note that this...

Hi Anton, Where can I get gccas ? I am running Mac OS X 10.5.6 and I get the following error: xgcc: installation problem, cannot exec `gccas': No such file or directory make[2]: *** [libgcc/./_muldi3.o] Error 1 make[2]: *** Waiting for unfinished jobs.... xgcc: installation problem, cannot exec `gccas': No such file or directory make[2]: *** [libgcc/./_negdi2.o] Error 1 make[1]:

...;>> >>> On Sat, 6 May 2006, Greg Pettyjohn wrote: >>> >>>> Now I'm having problems with this: >>>> >>>> llvm-ar rc ./libgcc.a libgcc/./_muldi3.o >>>> <and-lots-more-.o-files...> >>>> C:\msys\1.0\home\llvm_home\install\bin\llvm-ar.exe: <invalid>: >>>> path is not valid >>>> >>> >>> I've tracked this down in the debugger. It is indeed a bug. The >>> problem is >>> that Path::isValid() will reject a string containing "<" an...

Hi, I'm new to LLVM and I want to setup the Trident Compiler system on Mac OS X. I downloaded the llvm-gcc-4.2-2.4.source.tar.gz package, created a build directory and ran the following command to configure $ ../src/configure --program-prefix=llvm- --disable-bootstrap --enable- checking --enable-languages=c,c++ $ make -j 2 Configure works fine, but I get the following error

Hi all I compiled LLVM using ./configure --enable-assertions --enable-debug-runtime --enable-debug-symbols --enable-docs --enable-shared --enable-libffi --disable-optimized And then try to execute a .bc file using lli, ${LLVM_HOME}/Debug+Asserts/bin/lli -debug -force-interpreter ./jpegant.bc It reports : About to interpret: %9 = call i8* @memset(i8* %8, i32 0, i32 122)LLVM ERROR: Tried to execute an unknown external function: i8* (i8*, i32, i32)* memset Another case: ${LLVM_HOME}/Debug+Asserts/bin/lli -debug -force-int...

...5-06 at 16:43 -0400, Greg Pettyjohn wrote: >> >> On Sat, 6 May 2006, Greg Pettyjohn wrote: >> >>> Now I'm having problems with this: >>> >>> llvm-ar rc ./libgcc.a libgcc/./_muldi3.o <and-lots-more-.o-files...> >>> C:\msys\1.0\home\llvm_home\install\bin\llvm-ar.exe: <invalid>: path is not valid >>> >> >> I've tracked this down in the debugger. It is indeed a bug. The problem is >> that Path::isValid() will reject a string containing "<" and ">" on >> Windows. >>...

BTW: I've also had to make this change when building tools. (I'm building right now and noticed that it doesn't come up anymore, maybe someone checked it in in the last week or so) On Sat, 29 Apr 2006, Anton Korobeynikov wrote: > Hello, Jeff. > > You wrote Saturday, April 29, 2006, 10:45:02 PM: > > JC> Yes, I know mingw doesn't support dbghelp. I can still rant

...nge s- expressions. This is clumsy but it works at least. > There are some ocaml bindings in CVS by Gordon Henriksen :- > > http://llvm.org/viewvc/llvm-project/llvm/trunk/bindings/ocaml/ > > Dont know anything about them but they seem pritty extensive. You can find them in $LLVM_HOME/bindings/ocaml. According to their author they are not yet complete enough for a full front end but when I looked at them some weeks ago they seemed to already cover the code generation part completely. HTH, Jan

...>>>> On Sat, 6 May 2006, Greg Pettyjohn wrote: >>>> >>>>> Now I'm having problems with this: >>>>> >>>>> llvm-ar rc ./libgcc.a libgcc/./_muldi3.o <and-lots-more-.o-files...> >>>>> C:\msys\1.0\home\llvm_home\install\bin\llvm-ar.exe: <invalid>: path is >>>>> not valid >>>>> >>>> >>>> I've tracked this down in the debugger. It is indeed a bug. The problem >>>> is >>>> that Path::isValid() will reject a string cont...

Hello, Jeff. You wrote Saturday, April 29, 2006, 10:45:02 PM: JC> Yes, I know mingw doesn't support dbghelp. I can still rant about it :) ;) Well. Maybe this library will be included in some next versions of mingw's win32api package. Anyway, we can make such library just "on-fly" from the corresponding .dll. JC> This is what's already there. What changed? Maybe

Hi, I'm having a problem with opt. According to the "Writing an LLVM Pass" tutorial, all I have to do to get the Hello pass to work is: cd ${LLVM_HOME}/llvm/lib/Transforms/Hello gmake cd $MYTEST opt -load ${OBJ_ROOT}/lib/Release/libhello.so -hello < something.bc > /dev/null First (just as a friendly reminder), someone may want to go back and double check a bunch of the command lines given in these tutorials. It looks like the opt to...

On Wed, Jul 09, 2003 at 10:47:14AM -0500, Nicholas Rizzolo wrote: > I'm having a problem with opt. According to the "Writing an LLVM Pass" > tutorial, all I have to do to get the Hello pass to work is: > > cd ${LLVM_HOME}/llvm/lib/Transforms/Hello > gmake > cd $MYTEST > opt -load ${OBJ_ROOT}/lib/Release/libhello.so -hello < something.bc > /dev/null That's pretty much it, assuming a couple of prerequisites, see below. > First (just as a friendly reminder), someone may want to go back a...