similar to: [LLVMdev] running tblgen

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]: ***

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

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' > llvm[1]: Constructing LLVMBuild project information. > /usr/bin/env: python:

Hi Vadim, I am the book author of "Creating an LLVM Backend for the Cpu0 Architecture". Your question is right. More documents is good for programmer just like plentiful book in Linux Programming, even though the GCC backend compiler book is seldom. As you can see, I have let readers know how to write a RISC backend in my book but lack of the CISC backend features, like the complex

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 suspect some of the items are still unimplemented. The best thing

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 > configure: error: Unrecognized target

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

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

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 >

Hi, everyone. Does anyone faced with the MSVC Debug build issues of clang-tblgen and llvm-tblgen? I'm using Windows10 Pro. MSVC and GCC. Here is my cmake setup: cmake -GNinja ../llvm -DLLVM_ENABLE_PROJECTS=clang -DLLVM_TARGETS_TO_BUILD=X86 -DCMAKE_BUILD_TYPE=Debug When building debug with GCC, cmd shows next: D:\llvm-project\buildn2\bin>clang-tblgen.exe --version LLVM

I have tried to do this work, to link them to libLLVM-3.3.so or/and libclang.so, but failed. Only succeed with llvm-tblgen, to link it to shared libraries instead of static ones. Then I tried to link clang to libclang.so, exclude the clang***.a files that included in libclang.so. but it show many "undefined reference" error. Thanks.

The attached patch fixes an error message emitted by tblgen when no subclasses of 'Target' are defined. In the current version the message is ERROR: Multiple subclasses of Target defined! which is a bit confusing. - Volodya -------------- next part -------------- A non-text attachment was scrubbed... Name: CodeGenWrappers.diff Type: text/x-diff Size: 1057 bytes Desc: not available

Hi LLVM'ers I got this error: ------------------------------- gmake[3]: Entering directory `/usr/local/src/llvm/lib/Target/X86' Building X86.td register information header with tblgen tblgen: Assertion failed: "Buffer[Length-1] == '"'", file FileLexer.l, line 114 gmake[3]: *** [X86GenRegisterInfo.h.inc] Abort trap (core dumped) gmake[3]: Leaving directory

On Wed, 18 Aug 2004, Henrik Bach wrote: > I think I've found the error: > > The Buffer contains: include "../Target.td" and length is 23. > The file that tablegen is looking for is therefore: "../Target.td". > > However, in the assertion you assert an empty buffer and that is not what > you want, I suppose. If you change line 114 to != instead ==, then

On Tue, Aug 17, 2004 at 09:39:23PM -0500, Chris Lattner wrote: > > The next problem, on my system (Interix - you remember - Hey, some > > LLVM program is working :O ), is however, that it cannot find the > > ../Target.td file. At the moment I see some more bugs luring ahead > > in the TableGen code. More on that later. > > I'm sure this is because you hacked the

>From: Jeff Cohen <jeffc at jolt-lang.org> >Date: Sat, 25 Sep 2004 15:26:56 -0700 > >Yes. You need to link with dbghelp.lib and psapi.lib. There are >pragmas to force this, but not surprisingly gcc does not honor Microsoft >pragmas. I can't find the above libs. Where are they located on your system? Are there any dll pendants? Henrik

>From: Jeff Cohen <jeffc at jolt-lang.org> >Date: Tue, 28 Sep 2004 13:05:16 -0700 > >They are part of the Platform SDK from Microsoft, part of Visual Studio. >They correspond to Window system DLLs dbghelp.dll and psapi.dll in Arrrggg, I forget this relation... >\winnt\system32. If you do not have these libs, then you are out of >luck. Mingw should have provided them