725584e26d
Summary: Make it possible to feed runtime information back to tablegen to enable profile-guided tablegen-eration, detection of untested tablegen definitions, etc. Being a cross-compiler by nature, LLVM will potentially collect data for multiple architectures (e.g. when running 'ninja check'). We therefore need a way for TableGen to figure out what data applies to the backend it is generating at the time. This patch achieves that by including the name of the 'def X : Target ...' for the backend in the TargetRegistry. Reviewers: qcolombet Reviewed By: qcolombet Subscribers: jholewinski, arsenm, jyknight, aditya_nandakumar, sdardis, nemanjai, ab, nhaehnle, t.p.northover, javed.absar, qcolombet, llvm-commits, fedor.sergeev Differential Revision: https://reviews.llvm.org/D39742 llvm-svn: 318352
24 lines
701 B
C++
24 lines
701 B
C++
//===-- SystemZTargetInfo.cpp - SystemZ target implementation -------------===//
|
|
//
|
|
// The LLVM Compiler Infrastructure
|
|
//
|
|
// This file is distributed under the University of Illinois Open Source
|
|
// License. See LICENSE.TXT for details.
|
|
//
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
#include "SystemZ.h"
|
|
#include "llvm/Support/TargetRegistry.h"
|
|
|
|
using namespace llvm;
|
|
|
|
Target &llvm::getTheSystemZTarget() {
|
|
static Target TheSystemZTarget;
|
|
return TheSystemZTarget;
|
|
}
|
|
|
|
extern "C" void LLVMInitializeSystemZTargetInfo() {
|
|
RegisterTarget<Triple::systemz, /*HasJIT=*/true> X(
|
|
getTheSystemZTarget(), "systemz", "SystemZ", "SystemZ");
|
|
}
|