similar to: [LLVMdev] [patch] SPARCV9 subtarget support

Hello, Nathan >   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

On 03/02/2010, at 10:16 PM, Anton Korobeynikov wrote: > Hello, Nathan > >> 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

Hello, Nathan >   I may need to clarify, sparcv9-* is used for the SPARCV9 ABI (ie 64-bit ABI), rather than the SPARCV9 CPU per se. It serves the same purpose as x86_64-* and powerpc64-*, which is to say it's associated with -m64, not -mcpu=v9 (although unsurprisingly -m64 does require a V9 or later CPU). I may be wrong, but I think the only distinction in ARM is between arm and thumb

Hi, 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 llvm::<unnamed>::JITResolver::CompilationCallback()':

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 >

Hello When I was using OpenSSH-2.9p2 in Solaris 8 sparcv9 (64bit) environment, I found some trouble that wtmpx has broken. The size of utmpx structure object becomes larger than 32 bit environment in sparcv9 environment.Therefore, instead of using utmpx structure object, using futmpx structure object is better. In sparcv9 environment, futmpx structure object is used instead of utmpx structure

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

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

Hi: When I tried to use llc -march=sparcv9 to compile some llvm .bc to SparcV9, I got such error: llc: /llvm/lib/Target/SparcV9/SparcV9RegInfo.h:62: virtual void llvm::TargetRegClassInfo::markColorsUsed(unsigned int, int, int, std::vector<bool, std::allocator<bool> >&) const: Assertion `UserRegType == RegTypeWanted && "Default method is probably incorrect for

I am new to LLVM, and I'm trying to compile llvm and llvm-gcc from subversion on a Solaris10/SPARC machine. I have already tried building llvm-2.4 on this machine, but it failed. I then tried the subversion sources (rev. # 65253 fro llvm and rev#65263 for llvm-gcc) and llvm at least builds correctly ( I however have not tried testing it!). I can execute binaries located in

Dear R-HELP, We are compiling R-2.12.1 for 64 bits onto a Sun Sparc machine below: SunOS 5.10 Generic_142900-13 sun4u sparc SUNW,Netra-T12 The source was compiled successfully with "gcc version 3.4.6" by using the default configuration and has produced R-2.12.1 in 32 bits. Compiling R-2.12.1 for the 64 bits by configuring the config.site file as follow: CC="gcc -m64"

Hi, I am trying to compile R-2.2.1 on Solaris 2.9 with a 64-bit build. Following the instructions in "R Installation and Adminstration", I changed the following settings in "config.site": CC="gcc -m64" F77="g77 -64" CXX="g++ -m64" LDFLAGS="-L/usr/local/lib/sparcv9 -L/usr/local/lib" But I got the following error messages:

Hello I'm having trouble building R under Unix. I've searched for information about it on google or the R database but I didn't find any answer on my problem. I would be thankful if somebody could help me working that out. The version of R I'm trying to build is R-2.4.0 and the architecture of solaris is sparc. Here's what I type. PATH=/opt/sfw/bin:$PATH export

sorry, llc -march=hexagon -mcpu=hexagonv2 test.ll -o test.s works. 2012/7/3 Triple Yang <triple.yang at gmail.com>: > hi, > > does someone notice that llc options "-march=hexagon" and > "-march-sparcv9" do not work well under llvm 3.1? > > Following is a brief description: > (1) test.c file > > int cmp(int i, int j) { > return

On 20/06/2008, at 3:22 PM, Chris Lattner wrote: > > On Jun 16, 2008, at 2:12 PM, heguojin at ict.ac.cn wrote: > >> Has anyone succeded ? > > This sounds like the sparc backed doesn't have inline asm support, > which isn't a surprise. I'd suggest disabling bootstrapping. That was going to be my guess (PR1557 I think it is). If I get some spare cycles in the

hi, does someone notice that llc options "-march=hexagon" and "-march-sparcv9" do not work well under llvm 3.1? Following is a brief description: (1) test.c file int cmp(int i, int j) { return (i>j)?1:0; } (2) test.ll file (clang -emit-llvm test.c -S -o test.ll) ; ModuleID = 'test.c' target datalayout =

Hi, all, I have been recently porting a backend for our experimental DSP. It has a regular register file for ALU, naming it R registers, and another register file (J registers) for memory access. Both R registers and J registers are 32-bit. Since LLVM cannot distinguish 32-bit integers or pointers during register allocation, I have to define J as 64-bit, although it's physically 32-bit. This

openssh 3.7p1 sshd on Solaris 8 / sparcv9: sshd runs fine, and starts to allow the login. However, when reading from /etc/default/login, I get a bus error. I am able to get sshd to work by commenting out these lines in session.c: 1015,1018c1015 < # ifdef HAVE_ETC_DEFAULT_LOGIN < read_etc_default_login(&env, &envsize, pw->pw_uid); < path =

Thanks. I wonder if we could use .bc file generated by X-86 llvm-gcc to feed SPARC llvm in some cases. -----Original Message----- From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Nathan Keynes Sent: Thursday, June 26, 2008 5:18 AM To: LLVM Developers Mailing List Subject: Re: [LLVMdev] Compile llvm-gcc-4.2 on sparc-sun-solaris2.10 On 20/06/2008, at 3:22

Hi! I can't build LLVM using GCC 4.1 (GCC CVS mainline) after http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20050328/025003.html Build terminated with error: /home/wanderer/pkg/build/llvm/src/llvm/lib/Target/SparcV9/ModuloScheduling/DependenceAnalyzer.cpp:25: error: explicit qualification in declaration of `llvm::FunctionPass* llvm::createDependenceAnalyzer()' at line: