search for: registertarget

...ibLLVMRiscoCodeGen.so -march=risco, but the target isn't recognized (it doesn't even appear in the llc -version output). The main steps I did for registering the backend were: - At RiscoTargetMachine.cpp: extern "C" void LLVMInitializeRiscoTarget() { // Register the target. RegisterTargetMachine<RiscoTargetMachine> X(TheRiscoTarget); RegisterAsmInfo<RiscoMCAsmInfo> A(TheRiscoTarget); } - At Risco.td: def Risco : Target { let InstructionSet = RiscoInstrInfo; } - At RiscoTargetInfo.cpp: Target llvm::TheRiscoTarget; extern "C" void LLVMInitializeRiscoTarg...

...tory 'TargetInfo'. The content of this file is: #include "mybackend.h" #include "llvm/Module.h" #include "llvm/Support/TargetRegistry.h" using namespace llvm; Target llvm::TheMybackendTarget; extern "C" void LLVMInitializeMybackendTargetInfo() { RegisterTarget<Triple::mybackend> X(TheMybackendTarget, "mybackend", "mybackend"); } Nothing special I think. The error message of the compiler is: llvm[1]: Compiling mybackendTargetInfo.cpp for Release+Asserts build synzenTargetInfo.cpp:17:26: error: no member named 'mybackend'...

...ain what goes wrong without the stub? It's the only part that > I didn't apply. The X86 backend doesn't get registered since there are no references to symbols in X86TargetMachine the object file is never pulled in from the library I create, and thus the static intializer for the RegisterTarget is never called... RegisterTarget<X86TargetMachine> X("x86", " IA-32 (Pentium and above)"); I've tried some other ways to resolve it, but so far I've had no luck .. any suggestions are appreciated, as this is a problem in other places as well - and I...

...thout the stub? It's the only part that > > I didn't apply. > > The X86 backend doesn't get registered since there are no references to > symbols in X86TargetMachine the object file is never pulled in from the > library I create, and thus the static intializer for the RegisterTarget > is never called... I'm not sure how your patch fixes it though. The only references added by your change would be within the X86 library. How does this change the situation? > RegisterTarget<X86TargetMachine> X("x86", " IA-32 (Pentium and above)"); >...

On Mon, 18 Oct 2004, Morten Ofstad wrote: > To reduce the number of mails, I also include my next patch -- X86 > specific code and inline assembly for Visual C, unfortunately I had to > use the nasty IncludeFile trick again to get the linker to work.. I applied most of this here: http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20041018/019493.html Can you explain what goes

Paolo Invernizzi wrote: > There was a similar problem some time ago, and was resolved with alloca. > I think it's a better solution to use the stack instead of the heap... I tend to agree, but the constructors won't get called if it's an object array -- anyway, this particular case there was no objects, just pointers and bools so alloca should be fine. I'll leave it to

I'm having a go at writing an LLVM backend for the WDC 65816. The documentation page on writing an LLVM backend<http://llvm.org/docs/WritingAnLLVMBackend.html>gives this example of target registration: extern "C" void LLVMInitializeSparcTargetInfo() { RegisterTarget<Triple::sparc, /*HasJIT=*/false> X(TheSparcTarget, "sparc", "Sparc"); } The part I'm wondering about is Triple::sparc. If I'm writing a target for a different architecture, is it necessary for that architecture to have an entry in Triple's ArchType...

...t1.s clang-8: warning: argument unused during compilation: '-march=baz' [-Wunused-command-line-argument] I'm concluding that I need to write a "consumer" of the -march and/or -mcpu options myself, but I can't find a canonical example of this anywhere. I've played with RegisterTarget, but the documentation is a bit too densely packed for me. Other CPUs like ARM and AArch64 work, and I can't figure out why. Can anyone please point me at how to canonically add a -march= or -mcpu= option to MSP430? I can take it from there. Thank you! M -- Mark R V Murray

...tool. Would you mind helping me again to resolve this problem? Thank you very much. Seung Jae Lee >>While making my code for LLVM backend, I'd indeed like to >>convert HLL to the text assembly code for my new >>architecture. >>I registered my target through >>RegisterTarget<XccTargetMachine> X("xcc", "XCC"); >>in XccTargetMachine.cpp. Your response: Make sure that the library is being linked into your tool. This requires adding code to llvm/autoconf/configure.ac (search for TARGETS_TO_BUILD, add yours). Then regenerate configure, t...

> You are the only one who response my problem. The others maybe don't > understand my questions....:( I'm also replying to the list. People are very nice and helpful! Plus, I am on vacation! :) > well....my questions are following. > 1. I wrote a very simple backend, but I dont know how to tell the llvm > compiler to use it. > I found something in "llc

...It's the only part that >>>I didn't apply. >> >>The X86 backend doesn't get registered since there are no references to >>symbols in X86TargetMachine the object file is never pulled in from the >>library I create, and thus the static intializer for the RegisterTarget >>is never called... > > I'm not sure how your patch fixes it though. The only references added by > your change would be within the X86 library. How does this change the > situation? Because I'm including the X86TargetMachine header from the application (Fibonacci.cp...

Howdy: I'm a newbie of LLVM. I want to make sure that my way is correct. Plz tell me... we design a new processor with a new arch. we wanna get a compiler as fast as possible. The target code of the new compiler is machine code. So, is it I just to create a whole new backend for our new processor, right? And then???? Thx.

> On Sep 1, 2016, at 9:20 PM, Greg Parker <gparker at apple.com> wrote: > >> On Sep 1, 2016, at 9:06 PM, llvm.buildmaster at lab.llvm.org wrote: >> >> The Buildbot has detected a new failure on builder sanitizer-x86_64-linux-fast while building llvm. >> Full details are available at: >>

...StringRef CPU, StringRef FS, Reloc::Model RM, CodeModel::Model CM) ; }; extern Target TheRxTarget; } 4) lib/Target/Rx/TargetInfo/RxTargetInfo.cpp using namespace llvm; Target llvm::TheRxTarget ; extern "C" void LLVMInitializeRxTargetInfo() { RegisterTarget<Triple::Rx> X(TheRxTarget, "rx", "Rx"); } extern "C" void LLVMInitializeRxTargetMC() {} 5) lib/Target/Rx/TargetInfo/Makefile LEVEL = ../../../.. LIBRARYNAME = LLVMRxInfo # Hack: we need to include 'main' target directory to grab private headers CPPFLAGS...