search for: allocatetarget

...tion   'e-m:o-i64:64-f80:128-n8:16:32:64-S128'   1 error generated. The target selection is a little tricky here and I wonder if it's on purpose or not. One solution is to add another line:   TT.setOS(llvm::Triple::UnknownOS); This line removes the OS info from my triple, so that the AllocateTarget() function no longer returns a DarwinX86_64TargetInfo from here: https://github.com/llvm-mirror/clang/blob/71928e1dab585f336f6d0fb337969eda00ccd19c/lib/Basic/Targets.cpp#L491 The problem with DarwinX86_64TargetInfo is, that it's hard-coded for Mach-O. It always sets the same data-layout string...

Thanks Tom for your help, it as indeed very easy to make the link with the linker (not sick joke). Unfortunately, clang generates object files for target x86_64, even though I try --target --triple, --arch, ... What is the trick to tell him which target to use ? -- Fred ps: not looked yet at inline assembly 2015-07-09 18:40 GMT+02:00 Tom Stellard <tom at stellard.net>: > On Thu, Jul

-march for clang and -march for llc do different things unfortunately. -march for clang at least on x86 is the same as -mcpu in llc. Which is an artifact of gcc compatibility. ~Craig On Sat, Mar 23, 2019 at 1:40 PM Doerfert, Johannes via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Oh, my bad. > > > Idk why llc seems to know that architecture but clang does not. > >

...ng/lib/Basic/Targets.cpp:6459:20: error: 'AK_ARMV8_2A' is not a member of 'llvm::AArch64::ArchKind' ArchKind = llvm::AArch64::ArchKind::AK_ARMV8_2A; ^ /export2/src/llvm-trunk/llvm/tools/clang/lib/Basic/Targets.cpp: In function 'clang::TargetInfo* AllocateTarget(const llvm::Triple&, const clang::TargetOptions&)': /export2/src/llvm-trunk/llvm/tools/clang/lib/Basic/Targets.cpp:9570:10: error: 'Bitrig' is not a member of 'llvm::Triple' case llvm::Triple::Bitrig: ^ /export2/src/llvm-trunk/llvm/tools/clang/lib/Basi...