similar to: [LLVMdev] LLVM build error (sparc gcc 3.2.2)

Displaying 20 results from an estimated 1000 matches similar to: "[LLVMdev] LLVM build error (sparc gcc 3.2.2)"

2004 Sep 29
0
[LLVMdev] LLVM build error (sparc gcc 3.2.2)
On Wed, Sep 29, 2004 at 06:44:50PM -0400, Shukang Zhou wrote: > I met some errors when I tried to build LLVM. The tar file is > llvm-1.3.tar.gz. I am using a sparc machine with gcc 3.2.2. > > ------------- > Compiling SparcV9CodeEmitter.cpp > /uf24/zhou/research/llvm/src/lib/Target/SparcV9/SparcV9CodeEmitter.cpp: In > static member function `static void >
2004 Oct 10
2
[LLVMdev] building LLVM (question about ELF class)
Hi, Thanks for the replies in the mailing list. I made some progress in building LLVM, but I still have a problem about ELF class. I am working with LLVM on a sparcv9 machine, while the gcc is configured to emit 32-bit binary by default. After executing "configure --with-llvmgccdir=... --enable-jit", I modified Makefile.config so it contains CXX = g++ -mcpu=v9 -m64 CC := gcc -mcpu=v9
2004 Oct 07
2
[LLVMdev] problem with lli (llvm 1.3)
Hi, I am working with llvm 1.3 on a sparcv9 machine. I have successfully built llvm and llvm-gcc frontend. I can run many tools including llvmgcc, llvm-dis, and llc. After using /opt/SUNWspro/bin/cc to assemble .s file into a program binary, I can run the binary correctly as well. I am interested in the JIT compiler (lli). When I directly run the LLVM bytecode using interpretation ("lli
2004 Oct 07
2
[LLVMdev] problem with lli (llvm 1.3)
Thanks Misha. I tried the "gcc -dM -E /tmp/file.c | grep __sparcv9" but there was no output. Maybe this is the probelm, I do have CXX = g++ -mcpu=v9 CC := gcc -mcpu=v9 in the Makefile.config. Do I need to add -m64 as well? Thanks. Shukang On Thu, 7 Oct 2004, Misha Brukman wrote: > Is your compiler configured to define __sparcv9 when it compiles? > The following should tell
2010 Feb 03
4
[LLVMdev] [patch] SPARCV9 subtarget support
Hi all, I've put together some preliminary patches to add frontend support for the sparcv9-* subtarget (ie 64-bit SPARC), modelled on the corresponding x86-64 code - do these look reasonable for inclusion? This doesn't address the codegen side of things yet (isel falls over when trying to actually emit 64-bit code), but at least bitcode generation looks correct now. Tested on
2004 Nov 11
1
R with Sun Studio Fortran 95 compiler
Hi, I am trying to compile R 1.9.1 and 2.0.0 on Solaris 2.8 with Sun Studio Fortran 95 compiler but I have obtained some errors which I enclose. I have compiled R with g77 GNU compiler and it was OK. Does anyone know if R 2.0.0 has been successfully built on Solaris 2.8 with Sun Studio Fortran 95 compiler? or at least, How could I achieve this? The R installation manual does not have any
2016 Dec 12
1
Problem about 128bit floating-point operations in x86 machines
Hello, I'm making a compiler utilizing LLVM. Because I want the compiler to support 128bit floating-point operations, I added the code for 128bit floating-point operations and tested these operations in i686, x86_64, SPARCv8 and SPARCv9 machines. Generated codes by LLVM operated normally when using x86_64, SPARCv8 and SPARCv9 machines, but generated codes in a x86 machine produce wrong
2005 Jun 17
1
[LLVMdev] varargs heads up
Sometime this weekend (or today) vararg support will change. vanext will go away, and the intrinsic signatures will change. Backwards compatibility code will be included so front ends won't need to change initially (after that code is tested, then we will upgrade llvm-gcc). What should work after the transition: All Pattern based ISels (default on x86, PPC, Alpha, IA64) Existing .bc and .ll
2004 Oct 07
0
[LLVMdev] problem with lli (llvm 1.3)
On Thu, Oct 07, 2004 at 06:46:18PM -0400, Shukang Zhou wrote: > Thanks Misha. I tried the "gcc -dM -E /tmp/file.c | grep __sparcv9" > but there was no output. Maybe this is the probelm, I do have > > CXX = g++ -mcpu=v9 > CC := gcc -mcpu=v9 > > in the Makefile.config. Do I need to add -m64 as well? Thanks. Just run the test that I mentioned before: > On Thu, 7
2001 Nov 04
4
Slow connection performance with ssh2
Hi, since I switched from SSH 1 to OpenSSH 2.9p2/2.9.9p2/3.0p1 Snapshot I suffer from awfully slow connection performance. Once the connection is established, performance is perfectly ok. Client Server (protocol 2 only) # time ssh -p 22222 xx id # time sshd -d -p 22222 real 0m13.340s real 0m13.900s user 0m7.860s
2009 Sep 09
4
'make install' fails on Solaris (PR#13946)
Full_Name: Bob Bownes Version: 2.9.2 OS: Solaris 10 Submission from: (NULL) (164.55.254.106) The sed lines in src/unix/Makefile confuse the grep distributed with Solaris that gets configured by ./configure. Switching from a separator of ':' to a separator of ',' fixes the problem. 76,77c76,77 < @$(SED) -e "s:@rhome:$(rhome):" -e
2010 Aug 16
19
v2.0.0 released
http://dovecot.org/releases/2.0/dovecot-2.0.0.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.0.tar.gz.sig As promised last Friday, here's the v2.0.0 release finally. I'm cautiously optimistic that v2.0.1 won't (have to) be released for a few weeks, since there was quite a lot of testing and fixing going on in the RC stage. Remember to read http://wiki2.dovecot.org/Upgrading/2.0
2010 Aug 16
19
v2.0.0 released
http://dovecot.org/releases/2.0/dovecot-2.0.0.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.0.tar.gz.sig As promised last Friday, here's the v2.0.0 release finally. I'm cautiously optimistic that v2.0.1 won't (have to) be released for a few weeks, since there was quite a lot of testing and fixing going on in the RC stage. Remember to read http://wiki2.dovecot.org/Upgrading/2.0
2004 Oct 11
0
Sun Forte 9 / configure compatability problem with 2.0/1.9.x (PR#7278)
Full_Name: Mike Pacey Version: 2.0, 1.9.x OS: Solaris 8 Submission from: (NULL) (194.80.32.8) Symptoms: -------------- It seems the latest version of the Sun Compiler Suite (Forte 9) has compatability issues with R's configure script. Starting with a fairly vanilla configure (I'm using 1.9.1 here, but I've replicated the problem on 1.9.0 and 2.0.0): % export CC=cc % export F77=f95
2004 Oct 07
0
[LLVMdev] problem with lli (llvm 1.3)
On Thu, Oct 07, 2004 at 06:22:34PM -0400, Shukang Zhou wrote: > I am working with llvm 1.3 on a sparcv9 machine. I have successfully > built llvm and llvm-gcc frontend. I can run many tools including > llvmgcc, llvm-dis, and llc. After using /opt/SUNWspro/bin/cc to > assemble .s file into a program binary, I can run the binary correctly > as well. > > I am interested in the
2004 Oct 07
1
[LLVMdev] problem with lli (llvm 1.3)
I'm sorry, I did not completely understand your email, let me clarify my response. On Thu, Oct 07, 2004 at 06:46:18PM -0400, Shukang Zhou wrote: > Thanks Misha. I tried the "gcc -dM -E /tmp/file.c | grep __sparcv9" > but there was no output. Maybe this is the probelm, I do have > > CXX = g++ -mcpu=v9 > CC := gcc -mcpu=v9 > > in the Makefile.config. Do I need
2010 Jul 21
3
smbd -D hangs
I'm testing both sunfreeware and official sun (sfw) samba on Solaris 10. For some reason since yesterday, the smbd process just "hangs" at the start. No log is generated on server side Where smbd is started, I can't find any open port on 139 or 145 My OS is Solaris 10 # uname -a SunOS labo2 5.10 Generic_142900-13 sun4v sparc SUNW,SPARC-Enterprise-T5120 #
2013 Apr 16
1
update config.guess and config.sub to support aarch64
Hello, would it be possible to update config.sub and config.guess to the latest versions (or at least version from automake-1.13.1) in order to support new architectures based on the ARM 64 bit CPU? Patch: http://plautrba.fedorapeople.org/openssh/openssh-latest-config.sub-config.guess.patch Related Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=926284 Thanks, Petr
2005 Jan 28
2
[LLVMdev] llc -load
Howdy everybody. I'm trying hard to load my backend. But I got problems. I took the target SparcV8 for lab. 1. mark all of the code in the bool SparcV8TargetMachine::addPassesToEmitAssembly(PassManager &PM,std::ostream &Out) and make it return false.( Of course I mark the // Output assembly language. PM.add(createSparcV8CodePrinterPass(Out, *this));) 2. generate the
2009 Oct 30
2
[LLVMdev] Should LLVM JIT default to lazy or non-lazy?
On 2009-10-29 23:55, Jeffrey Yasskin wrote: > On Thu, Oct 29, 2009 at 2:30 PM, Nicolas Geoffray > <nicolas.geoffray at lip6.fr> wrote: > >> Hi Jeffrey, >> >> Jeffrey Yasskin wrote: >> >>> Cool, I'll start implementing it. >>> >>> >> Great! Thanks. >> >> Just to clarify things: on my end, it