search for: registertargetmachin

...he 64-bit target. And the 16-bit target too. And nothing seems to have broken AFAICT... --- a/lib/Target/X86/X86TargetMachine.cpp +++ b/lib/Target/X86/X86TargetMachine.cpp @@ -24,8 +24,9 @@ using namespace llvm; extern "C" void LLVMInitializeX86Target() { // Register the target. + RegisterTargetMachine<X86_32TargetMachine> W(TheX86_16Target); RegisterTargetMachine<X86_32TargetMachine> X(TheX86_32Target); - RegisterTargetMachine<X86_64TargetMachine> Y(TheX86_64Target); + RegisterTargetMachine<X86_32TargetMachine> Y(TheX86_64Target); } @@ -74,7 +75,7 @@ X86_32TargetMa...

On Dec 23, 2014, at 10:28 AM, Chris Bieneman <beanz at apple.com> wrote: >>> It should be straight-forward to have something like LLVMInitializeX86Target/RegisterTargetMachine install the intrinsics into a registry. >> >> I tried doing that a few years ago. It’s not nearly as easy as it sounds because we’ve got hardcoded references to various target intrinsics scattered throughout the code. > > I was just writing to say exactly this. There are a numb...

...move to a model where intrinsic tables are registered by any targets that are activated. That would allow the intrinsic tables (including these switch/lookup mapping tables) to be in the target that uses them. > > It should be straight-forward to have something like LLVMInitializeX86Target/RegisterTargetMachine install the intrinsics into a registry. I tried doing that a few years ago. It’s not nearly as easy as it sounds because we’ve got hardcoded references to various target intrinsics scattered throughout the code. -------------- next part -------------- An HTML attachment was scrubbed... URL: <h...

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

...t mailing list target, but I'm trying out the new LLVM 7.0 packages found at http://apt.llvm.org by porting over an existing LLVM 6.0 project of ours to the new version. In doing so, I found that the executable always segfaulted at the same spot with no explanation: 0x0000000000fefe33 in llvm::RegisterTargetMachine<llvm::X86TargetMachine>::Allocator(llvm::Target const&, llvm::Triple const&, llvm::StringRef, llvm::StringRef, llvm::TargetOptions const&, llvm::Optional<llvm::R eloc::Model>, llvm::Optional<llvm::CodeModel::Model>, llvm::CodeGenOpt::Level, bool) () This happens if I...

...#39;m trying out the > new LLVM 7.0 packages found at http://apt.llvm.org by porting over an > existing LLVM 6.0 project of ours to the new version. In doing so, I found > that the executable always segfaulted at the same spot with no explanation: > > 0x0000000000fefe33 in > llvm::RegisterTargetMachine<llvm::X86TargetMachine>::Allocator(llvm::Target > const&, llvm::Triple const&, llvm::StringRef, llvm::StringRef, > llvm::TargetOptions const&, llvm::Optional<llvm::R > eloc::Model>, llvm::Optional<llvm::CodeModel::Model>, > llvm::CodeGenOpt::Level, bool) (...

...of 1: ==4153== Invalid read of size 1 ==4153==    at 0x4AFEE0: llvm::optional_detail::OptionalStorage<llvm::Reloc::Model, true>::OptionalStorage(llvm::optional_detail::OptionalStorage<llvm::Reloc::Model, true> const&) (in /home/preejackie/kld/toy) ==4153==    by 0x4B098D: llvm::RegisterTargetMachine<llvm::X86TargetMachine>::Allocator(llvm::Target const&, llvm::Triple const&, llvm::StringRef, llvm::StringRef, llvm::TargetOptions const&, llvm::Optional<llvm::Reloc::Model>, llvm::Optional<llvm::CodeModel::Model>, llvm::CodeGenOpt::Level, bool) (in /home/preejack...

...ackages found at http://apt.llvm.org by porting over an >>> existing LLVM 6.0 project of ours to the new version. In doing so, I found >>> that the executable always segfaulted at the same spot with no explanation: >>> >>> 0x0000000000fefe33 in >>> llvm::RegisterTargetMachine<llvm::X86TargetMachine>::Allocator(llvm::Target >>> const&, llvm::Triple const&, llvm::StringRef, llvm::StringRef, >>> llvm::TargetOptions const&, llvm::Optional<llvm::R >>> eloc::Model>, llvm::Optional<llvm::CodeModel::Model>, >>>...

Circling back to Chandler on file size differences. Here are the highlights of what is different. For my analysis I built LLVM and Clang using a clang built with my patches. The same clang was used for the baseline and the stripped build. I used the following CMake command: cmake -G "Sublime Text 2 - Ninja" -DCMAKE_BUILD_TYPE=Release -DLLVM_BUILD_LLVM_DYLIB=Yes

...clattner at apple.com <mailto:clattner at apple.com>> wrote: >> >> On Dec 23, 2014, at 10:28 AM, Chris Bieneman <beanz at apple.com <mailto:beanz at apple.com>> wrote: >>>>> It should be straight-forward to have something like LLVMInitializeX86Target/RegisterTargetMachine install the intrinsics into a registry. >>>> >>>> I tried doing that a few years ago. It’s not nearly as easy as it sounds because we’ve got hardcoded references to various target intrinsics scattered throughout the code. >>> >>> I was just writing to sa...

Hi all :) I'm new to llvm! I'm going through the kaleidoscope : compiling llvm IR to object code tutorial, code in the listings breaks and causes a segmentation fault. After some investigation through gdb, probably this constructor call, causing the segfault. |Program received signal SIGSEGV, Segmentation fault.|| ||0x00000000004afee0 in

hacker cling wrote: > Hello all, > I was playing with LLVM pass. I changed the > lib/Transforms/Hello/Hello.cpp 's content to be my own pass. Then I make > install the pass and use an example test1.c to see whether it works or > not. When I run example using the following command: > clang -emit-llvm test1.c -c -o test1.bc > opt -load

Hello all, I was playing with LLVM pass. I changed the lib/Transforms/Hello/Hello.cpp 's content to be my own pass. Then I make install the pass and use an example test1.c to see whether it works or not. When I run example using the following command: clang -emit-llvm test1.c -c -o test1.bc opt -load ../build_llvm/Debug+Asserts/lib/LLVMHello.so -hello < test1.bc > /dev/null It

..._CURRENT_BINARY_DIR}/.. $ \ {CMAKE_CURRENT_SOURCE_DIR}/.. ) add_llvm_library(LLVMRxInfo RxTargetInfo.cpp ) add_llvm_library_dependencies(LLVMRxInfo LLVMSupport LLVMTarget ) 7) lib/Target/Rx/RxTargetMachine.cpp using namespace llvm; extern "C" void LLVMInitializeRxTarget() { RegisterTargetMachine<RxTargetMachine> X(TheRxTarget); } RxTargetMachine::RxTargetMachine(const Target &T, StringRef TT, StringRef CPU, StringRef FS, Reloc::Model RM, CodeModel::Model CM) : LLVMTargetMachine(T,...

...#include "llvm/PassManager.h" +#include "llvm/Support/Debug.h" +#include "llvm/Support/raw_ostream.h" #include "llvm/Support/TargetRegistry.h" using namespace llvm; + + extern "C" void LLVMInitializeMipsTarget() { // Register the target. RegisterTargetMachine<MipsebTargetMachine> X(TheMipsTarget); @@ -42,7 +56,7 @@ MipsTargetMachine(const Target &T, StringRef TT, CodeGenOpt::Level OL, bool isLittle) : LLVMTargetMachine(T, TT, CPU, FS, Options, RM, CM, OL), - Subtarget(TT, CPU, FS, isLittle, RM), +...

On Thu, Mar 28, 2013 at 12:22 PM, Nadav Rotem <nrotem at apple.com> wrote: > IMHO the right way to handle target function attributes is to > re-initialize the target machine and TTI for every function (if the > attributes changed). Do you have another solution in mind ? I don't really understand this. TargetMachine and TTI may be quite expensive to initialize. Doing so for

...t; +#include "llvm/Support/raw_os_ostream.h" > +#include "llvm/Transforms/IPO.h" > +#include "llvm/Transforms/Scalar.h" > + > +using namespace llvm; > + > +extern "C" void LLVMInitializeAMDGPUTarget() { > + // Register the target > + RegisterTargetMachine<AMDGPUTargetMachine> X(TheAMDGPUTarget); > +} > + > +AMDGPUTargetMachine::AMDGPUTargetMachine(const Target &T, StringRef TT, > + StringRef CPU, StringRef FS, > + TargetOptions Options, > + Reloc::Model RM, CodeModel::Model CM, > + CodeGenOpt::Level OptLevel &gt...