search for: spra1c07

I am currently trying to build the CVS version of LLVM, and no matter what I do, ./configure always reports that llvm-gcc cannot be found or is not working. I currently have the LLVM 1.4 llvm-gcc binaries. My path is set correctly: rn-spra1c07:~/llvm/llvm ejones$ which llvm-gcc /Users/ejones/llvm/cfrontend/ppc/llvm-gcc/bin/llvm-gcc rn-spra1c07:~/llvm/llvm ejones$ which llvm-g++ /Users/ejones/llvm/cfrontend/ppc/llvm-gcc/bin/llvm-g++ So LLVM is on my path, and I ran configure with: ./configure --with-llvmgccdir=/Users/ejones/llvm/cfron...

...ed C test case. The program mmaps a file called 'data,' prints the last byte, truncates the file, then tries to read the last byte again. It causes a Bus Error on both the RedHat system and my Mac OS X workstation. Hence, this appears to be valid (or at least common) mmap behaviour. rn-spra1c07:~ ejones$ dd if=/dev/zero of=data bs=1 count=4096 4096+0 records in 4096+0 records out 4096 bytes transferred in 0.067263 secs (60895 bytes/sec) rn-spra1c07:~ ejones$ ./mmaptest last byte = 0x00 Bus error I can also reproduce it with a minimal LLVM example, also attached. That program needs the &...

...19 at 16:57, Evan Jones wrote: > I am currently trying to build the CVS version of LLVM, and no matter > what I do, ./configure always reports that llvm-gcc cannot be found or > is not working. I currently have the LLVM 1.4 llvm-gcc binaries. My > path is set correctly: > > rn-spra1c07:~/llvm/llvm ejones$ which llvm-gcc > /Users/ejones/llvm/cfrontend/ppc/llvm-gcc/bin/llvm-gcc > rn-spra1c07:~/llvm/llvm ejones$ which llvm-g++ > /Users/ejones/llvm/cfrontend/ppc/llvm-gcc/bin/llvm-g++ > > > So LLVM is on my path, and I ran configure with: > > ./configure &g...

...he correct behavior for mmap in such a situation. The mapped file, when it is truncated, invalidates the memory corresponding to truncated portion of the file. The memory is taken out of the virtual memory table so that any attempt to access generates a, you guessed it, bus error. > > rn-spra1c07:~ ejones$ dd if=/dev/zero of=data bs=1 count=4096 > 4096+0 records in > 4096+0 records out > 4096 bytes transferred in 0.067263 secs (60895 bytes/sec) > rn-spra1c07:~ ejones$ ./mmaptest > last byte = 0x00 > Bus error > > I can also reproduce it with a minimal LLVM example,...

Evan, Your patch uses an operating system call that is not portable. All non-portable code needs to be located in the lib/System library. I'm not sure why this problem appears on an old Red Hat system. Perhaps the C++ io library is not up to snuff on that platform? What compiler are you using? Reid. Evan Jones wrote: > I ran the LLVM regression tests today (via make check) and

I ran the LLVM regression tests today (via make check) and noticed that llvm-ranlib crashes with a Bus Error on my test system (a fairly old RedHat 9 system), using the latest CVS version. I did some digging and I think I know what the problem is, and I have attached a quick and dirty patch that fixes the problem for me, but I need a suggestion about how it should be integrated properly. Here