similar to: [LLVMdev] llc -load

On Tue, 25 Jan 2005, s88 wrote: > Thank you... > I am preparing to build a simple C compiler for our new architecture. > According to your suggestion. I try to dynamically load my backend. > But I got the error message : > llc : target 'Your_Arch' does not support static compilation! > could you tell me where is this problem? A useful tool in llvm is named

Thank you... I am preparing to build a simple C compiler for our new architecture. According to your suggestion. I try to dynamically load my backend. But I got the error message : llc : target 'Your_Arch' does not support static compilation! could you tell me where is this problem? On Mon, 24 Jan 2005 22:53:15 -0600 (CST), Chris Lattner <sabre at nondot.org> wrote: > On

> I can run that pass through opt on the bytecode emitted by gcc frontend > through opt tool. However, I want that Pass1 to be the part of the > actual GCC compiler. I want to know how I can position Pass1 among > other passes /optimizations/ code generations. I had a similar question and Chris recommended that I edit the addPassesToEmitAssembly method. Quoting him: "

I found 179 more *.{c,cpp,h} files with tabs. Unfortunately, the tabs stops used vary so blindly expanding them messes up alignment in many cases :( Index: examples/BFtoLLVM/BFtoLLVM.cpp Index: include/llvm/AbstractTypeUser.h Index: include/llvm/GlobalVariable.h Index: include/llvm/InstrTypes.h Index: include/llvm/IntrinsicInst.h Index: include/llvm/ADT/PostOrderIterator.h Index:

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

Anton Korobeynikov wrote: > The patch is incorrect and the problems you're seeing are caused by > your patch, since sparc != sparc64. > In LLVM sense "sparc" means "sparc with ILP32 architecture model", > llvm does not support anything 64 bit in sparc world SparcTargetMachine.h file lists SparcV9TargetMachine as 64-bit machine and SparcV8TargetMachine as

'collect2.exe' is an internal version of 'ld' called by GCC The GCC command line is :- g++ -I/usr/build/llvm-2/tools/llc -I/usr/src/llvm/tools/llc -I/usr/build/llvm-2/ include -I/usr/src/llvm/include -I/usr/build/llvm-2/include -I/usr/src/llvm/incl ude -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -Wall -W -Wwrite-strings -Wno-unused -g -D_DEBUG -v -o /usr/build/llvm-2/Debug/bin/llc.exe

I wonder in what cases FunctionPass is better that Pass. For example, addPassesToEmitAssembly takes PassManger and addPassesToJITCompile takes FunctionPassManager. Another question is about FunctionPassManager::run(Function&) and FunctionPass(Function&). The former calls the later, which is fine, but the latter looks like this: bool FunctionPass::run(Function &F) { if

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 >

Reid, Getting the same error again :-( /usr/gcc/gcc-3.4.3/libexec/gcc/i686-pc-cygwin/3.4.3/collect2.exe -Bdynamic --dl l-search-prefix=cyg -o /usr/build/llvm-2/Debug/bin/llc.exe /lib/crt0.o -L/usr/bu ild/llvm-2/Debug/lib -L/usr/build/llvm-2/Debug/bin -L/usr/gcc/gcc-3.4.3/lib/gcc/ i686-pc-cygwin/3.4.3 -L/usr/gcc/gcc-3.4.3/lib/gcc/i686-pc-cygwin/3.4.3/../../..

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

hello... I have finish my backend. But I dont know how to install my backend... llc -load=???Load what?? Can anyone teach me? thanx.

Hi again, I have put together a "blank skeleton" for a X86NASMPrinter class, with effectively the same behaviour as the X86IntelAsmPrinter class. I had to do this within the X86AsmPrinter.cpp file rather than as a separate source file as the dependancies were so. Please do not commit this yet, I have included it not for confidence sake :)) I do not know whether it is a good idea to

Suppose, I have a Pass1 implemented as a subclass of Pass, with source code in the directory of llvm source base( transform/analyze ) I can run that pass through opt on the bytecode emitted by gcc frontend through opt tool. However, I want that Pass1 to be the part of the actual GCC compiler. I want to know how I can position Pass1 among other passes /optimizations/ code generations. e.g if

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

On Mon, 24 Oct 2005, Vladimir A. Merzliakov wrote: >>> 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

>> 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 <<

On Thu, 24 Jun 2004, Vladimir Prus wrote: > I wonder in what cases FunctionPass is better that Pass. For example, > addPassesToEmitAssembly takes PassManger and addPassesToJITCompile takes > FunctionPassManager. Here's a simple way to look at it. Use a Function pass whenever you can. A function pass will always work where a Pass works (it derives from pass as you've noticed),

Hi, I am trying to read the "credit.lisp" file of the Japanese credit database in UCI repository, but it is in lisp format which I do not know how to read. I have not found how to do that in the foreign library http://archive.ics.uci.edu/ml/datasets/Japanese+Credit+Screening <http://archive.ics.uci.edu/ml/datasets/Japanese+Credit+Screening> Could anyone help me? Best

On Tue, 25 Jan 2005, s88 wrote: > hello... > I have finish my backend. But I dont know how to install my backend... > llc -load=???Load what?? > Can anyone teach me? > thanx. There are two ways to do this. You can either link the backend directly into llc (like the X86 or PowerPC backends, see tools/llc/Makefile), or you can dynamically load the backend. To dynamically load