search for: khoptynets

Hello everyone! I've started to implement a ColdFire backend, but there are some troubles during configuring: $ ../llvm/configure --enable-targets=x86,x86_64,coldfire ... ... ... checking whether byte ordering is bigendian... no configure: error: Unrecognized target coldfire configure: error: ../../../llvm/projects/sample/configure failed for projects/sample I've added ColdFire to : 1)

Hello developers! Could you, please, inform me about actual open projects? Where can I find this information? Does this list contains up to date information http://llvm.org/OpenProjects.html#new ? -- Regards, Vadim. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120922/3db4debe/attachment.html>

On 9/22/12 9:01 AM, Vadim Khoptynets wrote: > Hello developers! > > Could you, please, inform me about actual open projects? Where can I > find this information? Does this list contains up to date information > http://llvm.org/OpenProjects.html#new ? I'm not sure if all of the information is up to date, but I sus...

On Fri, Feb 01, 2013 at 04:43:59PM +0200, Vadim Khoptynets wrote: > Hello everyone! > > I've started to implement a ColdFire backend, but there are some troubles > during configuring: > > $ ../llvm/configure --enable-targets=x86,x86_64,coldfire > ... > ... > ... > checking whether byte ordering is bigendian... no > co...

Hello to everyone! I've configured LLVM by "../llvm/configure". But when I run "gmake", I receive compilation error: llvm[2]: Linking Debug+Asserts executable llvm-tblgen /home/poiuj/dev/llvm/build/Debug+Asserts/lib/libLLVMSupport.a(FormattedStream.o):(.debug_loc+0x2a8): undefined reference to `.LCfI21' collect2: error: ld returned 1 exit status gmake[2]: ***

On Fri, Feb 1, 2013 at 4:01 PM, Tom Stellard <tom at stellard.net> wrote: > On Fri, Feb 01, 2013 at 04:43:59PM +0200, Vadim Khoptynets wrote: >> Hello everyone! >> >> I've started to implement a ColdFire backend, but there are some troubles >> during configuring: >> >> $ ../llvm/configure --enable-targets=x86,x86_64,coldfire >> ... >> ... >> ... >> checking whether by...

Hello everyone! Is there any documentation about LLVM backend implementation, except "Writing an LLVM backend"? I'm trying to write InstrFormats.td and InstrInfo.td for my backend now. After reading "Writing an LLVM backend" and "Creating an LLVM Backend for the Cpu0 Architecture", many black holes have remained. These tutorials describe it on concrete examples,

Vadim Khoptynets <vadya.poiuj at gmail.com> writes: > Hello, Óscar! > > I had some problems with my machine, so I've reistalled system and LLVM > repository. And now, I have another trouble during compilation: > make[1]: Entering directory `/media/data/dev/llvm/bin/tools/llvm-config' &...

Hello everyone! Could somebody advice me, how can I run llvm-tblgen to get MyTargetGenRegisterInfo.inc file to include in MyTargerRegisterInfo.h ? Unfortunately, I haven't found this information in "Writing an LLVM Compiler Backend" and "TableGen Fundamentals". -- Regards, Vadim. -------------- next part -------------- An HTML attachment was scrubbed... URL:

...ue.edu> wrote: > Hi Jonathan, please respond to this message from the LLVMdev mailing list: > > (also, you should subscribe to the LLVMdev and llvm-commits mailing > lists; if you haven't done so already) > > > ---------- Forwarded message ---------- > From: Vadim Khoptynets <vadya.poiuj at gmail.com> > Date: Sat, Feb 23, 2013 at 8:47 PM > Subject: [LLVMdev] backend documentation > To: llvmdev at cs.uiuc.edu > > > Hello everyone! > > Is there any documentation about LLVM backend implementation, except > "Writing an LLVM backend...

Hello everyone! There is segmentation fault during translating a simple function with my backend. Investigation with gdb has shown that address of InstrNameData array in generated file MyTargetGenInstrInfo.inc is out of bounds. Also, if I run llc without -view-dag options, NumOpcodes equals 0 inside llvm::MCInstrInfo::get function, although there are some instructions (they are appeared in

Hi Vadim, which compiler are you using to to the build, what platform are you on, how did you configure LLVM, clang etc ? Ciao, duncan. On 09/09/12 03:36, Vadim Khoptynets wrote: > Hello everyone! > > After I've checked out Clang and Compiler-RT repositories, I receive this error > during compilation: > > llvm[5]: Compiling PathDiagnostic.cpp for Debug+Asserts build > /media/data/dev/llvm/llvm/tools/clang/lib/StaticAnalyzer/Core/PathDiagnosti...

...pretty good; that is one area that can hang you up. A lot of the information that you want is in the documents that already exist but you have to get some experience with LLVM and go back and read and re-read them many times in order to grock the whole thing. Reed On 02/23/2013 05:47 PM, Vadim Khoptynets wrote: > Hello everyone! > > Is there any documentation about LLVM backend implementation, except > "Writing an LLVM backend"? I'm trying to write InstrFormats.td and > InstrInfo.td for my backend now. After reading "Writing an LLVM backend" > and "Cre...

Hello everyone! After I've checked out Clang and Compiler-RT repositories, I receive this error during compilation: llvm[5]: Compiling PathDiagnostic.cpp for Debug+Asserts build /media/data/dev/llvm/llvm/tools/clang/lib/StaticAnalyzer/Core/PathDiagnostic.cpp: In member function 'bool {anonymous}::CompareDiagnostics::operator()(const clang::ento::PathDiagnostic*, const

Hello everyone! Could somebody, advice me what's wrong with my AsmPrinter? I've created ColdFireAsmPrinter.cpp file, and added initialization: extern "C" void LLVMInitializeColdFireAsmPrinter() { RegisterAsmPrinter<ColdFireAsmPrinter> X(TheColdFireTarget); } But, unfortunately, after build AsmPrinters.def doesn't contain LLVM_ASM_PRINTER(ColdFire). Maybe I've