Displaying 4 results from an estimated 4 matches for "featurestring".
2010 May 28
0
[LLVMdev] how to get TargetData?
For those targets supported by LLVM, you can get their TargetData by
creating TargetMachine first (take X86 as example):
==== BEGIN CODE SNIPPET ====
const std::string TripleStr = "i686-unknown-linux"; // hard coded for
example
const std::string FeatureStr = ""; // hard coded for example
std::string Err;
const Target* T;
TargetMachine* TM = NULL;
const
2010 May 28
4
[LLVMdev] how to get TargetData?
Dear all
I am trying to get the size of an LLVM pointer type.
getPrimitiveSizeInBits() returns 0 for it and the documentation for
isSized() suggest to use TargetData.
I figured out from Kaleidoscope example that one can get a pointer to
TagetData object through the execution engine but it seems to be an
overkill.
What is the right way to do it?
Best regards,
Victor
-------------- next part
2017 Aug 22
2
Subtarget Initialization in <ARCH>TargetMachine constructor
...(CM),
OL),
TLOF(make_unique<TargetLoweringObjectFileELF>()),
Subtarget(TT, CPU, FS, *this) {
initAsmInfo();
}
LanaiTargetMachine::LanaiTargetMachine(const Target &T, const Triple &TT,
StringRef Cpu, StringRef
FeatureString,
const TargetOptions &Options,
Optional<Reloc::Model> RM,
Optional<CodeModel::Model> CodeModel,
CodeGenOpt::Level OptLevel, boo...
2014 Jun 01
4
[LLVMdev] Regression in 3.4's register allocator?
I think we have located the revision which fixes this regression: r206094
(or commit 6bb00df in llvm-mirror on GitHub). I have attached a patch which
can be applied to the current release_34 branch (tested against the
release_34 branch in llvm-mirror). With this patch the attached
reg-alloc-test.ll file doesn't fail with the "LLVM ERROR: ran out of
registers during register