search for: sparcv8

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 LLVMSparcV8.so...

Hi! I have some problems with build current CVS version LLVM using GCC 4.1.0 (GCC CVS mainline version). 1) Build terminate with error: llvm[3]: Compiling SparcV8CodeEmitter.cpp for Debug build /usr/home/wanderer/pkg/build/llvm/obj/lib/Target/SparcV8/SparcV8GenCodeEmitter.inc:11: error: definition of 'unsigned int llvm::<unnamed>::SparcV8CodeEmitter::getBinaryCodeForInstr(llvm::MachineInstr&)' is not in namespace enclosing 'llvm::&lt...

...;cannot use v8plus registers > in a non-v8plus target binary"). Is anyone who knows about this error? > Thanks a lot for your time and help. The backend is designed for SparcV9 and uses inline assembly, some of which may be V9-only. Your error indicates that your GCC was configured for SparcV8 instead. One way to check what your GCC thinks it's compiling for is as follows: % gcc -dumpmachine sparcv9-sun-solaris2.8 If your output is "sparcv8-...", then you may need to build a new version of GCC. -- Misha Brukman :: http://misha.brukman.net :: http://llvm.cs.uiuc.edu

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()':

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 result. Because Clang supports __float128 type, I also tried to test using Clang 3.9 version. However, I could not get the correct res...

On Mon, 24 Oct 2005, Vladimir A. Merzliakov wrote: > I have some problems with build current CVS version LLVM using GCC 4.1.0 (GCC > CVS mainline version). Thanks! > 1) Build terminate with error: > > llvm[3]: Compiling SparcV8CodeEmitter.cpp for Debug build > /usr/home/wanderer/pkg/build/llvm/obj/lib/Target/SparcV8/SparcV8GenCodeEmitter.inc:11: > error: definition of 'unsigned int Patch applied: http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20051017/028993.html > 2) Same error but some diff....

...art() to support thread restart https://reviews.llvm.org/D46467 [asan] Add argument to allow fake stack to be initialized during thread init https://reviews.llvm.org/D46468 [asan] Add target-specific files for Myriad RTEMS port https://reviews.llvm.org/D46469 [sanitizer] Port fast stack unwinder to sparcv8 Thanks, Walter

...ds 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 files What will break: SparcV9 SparcV8 (which doesn't currently support varargs, so not a big deal) Simple ISels for x86 and PPC (not the default codegen, so shouldn't really affect anybody) If you read a .ll or .bc file it will be converted to the new format and any file written will use the new instructions and intrinsics. A...

...e with >>> declaration in llvm::<unnamed> : > > Sorry for wrong comment. > Must be: > GCC 4.1.0 don't like definition member-functions in llvm namespace with > declaration in <global>::<unnamed> namespace Ahhh, ok, I see. I just applied a patch to SparcV8. With it, does this patch fix the problem? =================================================================== RCS file: /home/vadve/shared/PublicCVS/llvm/utils/TableGen/CodeEmitterGen.cpp,v retrieving revision 1.41 diff -u -r1.41 CodeEmitterGen.cpp --- CodeEmitterGen.cpp 19 Aug 2005 01:04:33 -...

>> Sorry for wrong comment. >> Must be: >> GCC 4.1.0 don't like definition member-functions in llvm namespace with >> declaration in <global>::<unnamed> namespace > > Ahhh, ok, I see. I just applied a patch to SparcV8. With it, does this > patch fix the problem? >- o << "namespace llvm {\n\n"; >+ //o << "namespace llvm {\n\n"; Yes :) Vladimir

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

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

...lib/Target/PowerPC/PPC32ISelPattern.cpp Index: lib/Target/PowerPC/PPC32ISelSimple.cpp Index: lib/Target/PowerPC/PPC32RegisterInfo.cpp Index: lib/Target/PowerPC/PPC64ISelPattern.cpp Index: lib/Target/PowerPC/PPC64RegisterInfo.cpp Index: lib/Target/Skeleton/SkeletonTargetMachine.cpp Index: lib/Target/SparcV8/SparcV8AsmPrinter.cpp Index: lib/Target/SparcV8/SparcV8ISelSimple.cpp Index: lib/Target/SparcV8/SparcV8TargetMachine.cpp Index: lib/Target/SparcV9/EmitBytecodeToAssembly.cpp Index: lib/Target/SparcV9/MachineFunctionInfo.cpp Index: lib/Target/SparcV9/MachineFunctionInfo.h Index: lib/Target/SparcV9/M...

>> 2) Same error but some diff. problem with AlphaCodeEmitter.cpp and >> PPCCodeEmitter.cpp: >> >> GCC don't like definition member-functions in global namespace with >> declaration in llvm::<unnamed> : Sorry for wrong comment. Must be: GCC 4.1.0 don't like definition member-functions in llvm namespace with declaration in

...; https://reviews.llvm.org/D46467 [asan] Add argument to allow fake stack to > be initialized during thread init > https://reviews.llvm.org/D46468 [asan] Add target-specific files for > Myriad > RTEMS port > https://reviews.llvm.org/D46469 [sanitizer] Port fast stack unwinder to > sparcv8 > > Thanks, > > Walter > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL:...

...don't immediately see a problem > with that. Note that a libcall doesn't necessarily mean using locks. With one exception, NetBSD provides lock-free CAS on all platforms for natural argument sizes. The intersection between platforms with MP support and platforms without hardware CAS is SPARCv8. Everything else works fine, even the libcall version. Joerg

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

...; https://reviews.llvm.org/D46467 [asan] Add argument to allow fake stack to > be initialized during thread init > https://reviews.llvm.org/D46468 [asan] Add target-specific files for > Myriad > RTEMS port > https://reviews.llvm.org/D46469 [sanitizer] Port fast stack unwinder to > sparcv8 > > Thanks, > > Walter > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL:...

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

...ws.llvm.org/D46467 [asan] Add argument to allow fake stack to >> be initialized during thread init >> https://reviews.llvm.org/D46468 [asan] Add target-specific files for Myriad >> RTEMS port >> https://reviews.llvm.org/D46469 [sanitizer] Port fast stack unwinder to >> sparcv8 >> Thanks, >> Walter >> _______________________________________________ >> LLVM Developers mailing list >> llvm-dev at lists.llvm.org >> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev