2010-11-14 19:53:02 +00:00
|
|
|
//===-- PPCMCInstLower.cpp - Convert PPC MachineInstr to an MCInst --------===//
|
|
|
|
//
|
|
|
|
// The LLVM Compiler Infrastructure
|
|
|
|
//
|
|
|
|
// This file is distributed under the University of Illinois Open Source
|
|
|
|
// License. See LICENSE.TXT for details.
|
|
|
|
//
|
|
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
//
|
|
|
|
// This file contains code to lower PPC MachineInstrs to their corresponding
|
|
|
|
// MCInst records.
|
|
|
|
//
|
|
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
|
2010-11-14 21:12:33 +00:00
|
|
|
#include "PPC.h"
|
2013-05-23 22:26:41 +00:00
|
|
|
#include "MCTargetDesc/PPCMCExpr.h"
|
2012-12-03 16:50:05 +00:00
|
|
|
#include "llvm/ADT/SmallString.h"
|
2013-04-27 00:43:16 +00:00
|
|
|
#include "llvm/ADT/Twine.h"
|
2010-11-14 19:53:02 +00:00
|
|
|
#include "llvm/CodeGen/AsmPrinter.h"
|
2010-11-15 02:46:57 +00:00
|
|
|
#include "llvm/CodeGen/MachineFunction.h"
|
2010-11-14 23:42:06 +00:00
|
|
|
#include "llvm/CodeGen/MachineModuleInfoImpls.h"
|
2013-02-20 00:31:54 +00:00
|
|
|
#include "llvm/IR/GlobalValue.h"
|
2010-11-14 23:42:06 +00:00
|
|
|
#include "llvm/MC/MCAsmInfo.h"
|
2010-11-14 19:53:02 +00:00
|
|
|
#include "llvm/MC/MCExpr.h"
|
|
|
|
#include "llvm/MC/MCInst.h"
|
2010-11-14 21:20:46 +00:00
|
|
|
#include "llvm/Target/Mangler.h"
|
2010-11-14 19:53:02 +00:00
|
|
|
using namespace llvm;
|
|
|
|
|
2010-11-14 23:42:06 +00:00
|
|
|
static MachineModuleInfoMachO &getMachOMMI(AsmPrinter &AP) {
|
|
|
|
return AP.MMI->getObjFileInfo<MachineModuleInfoMachO>();
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
static MCSymbol *GetSymbolFromOperand(const MachineOperand &MO, AsmPrinter &AP){
|
|
|
|
MCContext &Ctx = AP.OutContext;
|
|
|
|
|
|
|
|
SmallString<128> Name;
|
|
|
|
if (!MO.isGlobal()) {
|
|
|
|
assert(MO.isSymbol() && "Isn't a symbol reference");
|
|
|
|
Name += AP.MAI->getGlobalPrefix();
|
|
|
|
Name += MO.getSymbolName();
|
|
|
|
} else {
|
|
|
|
const GlobalValue *GV = MO.getGlobal();
|
|
|
|
bool isImplicitlyPrivate = false;
|
|
|
|
if (MO.getTargetFlags() == PPCII::MO_DARWIN_STUB ||
|
2010-11-15 03:13:19 +00:00
|
|
|
(MO.getTargetFlags() & PPCII::MO_NLP_FLAG))
|
2010-11-14 23:42:06 +00:00
|
|
|
isImplicitlyPrivate = true;
|
|
|
|
|
|
|
|
AP.Mang->getNameWithPrefix(Name, GV, isImplicitlyPrivate);
|
|
|
|
}
|
|
|
|
|
|
|
|
// If the target flags on the operand changes the name of the symbol, do that
|
|
|
|
// before we return the symbol.
|
2010-11-15 03:13:19 +00:00
|
|
|
if (MO.getTargetFlags() == PPCII::MO_DARWIN_STUB) {
|
2010-11-14 23:42:06 +00:00
|
|
|
Name += "$stub";
|
2013-04-27 00:43:16 +00:00
|
|
|
const char *PGP = AP.MAI->getPrivateGlobalPrefix();
|
|
|
|
const char *Prefix = "";
|
|
|
|
if (!Name.startswith(PGP)) {
|
|
|
|
// http://llvm.org/bugs/show_bug.cgi?id=15763
|
|
|
|
// all stubs and lazy_ptrs should be local symbols, which need leading 'L'
|
|
|
|
Prefix = PGP;
|
|
|
|
}
|
|
|
|
MCSymbol *Sym = Ctx.GetOrCreateSymbol(Twine(Prefix) + Twine(Name));
|
2010-11-14 23:42:06 +00:00
|
|
|
MachineModuleInfoImpl::StubValueTy &StubSym =
|
|
|
|
getMachOMMI(AP).getFnStubEntry(Sym);
|
|
|
|
if (StubSym.getPointer())
|
|
|
|
return Sym;
|
|
|
|
|
|
|
|
if (MO.isGlobal()) {
|
|
|
|
StubSym =
|
|
|
|
MachineModuleInfoImpl::
|
|
|
|
StubValueTy(AP.Mang->getSymbol(MO.getGlobal()),
|
|
|
|
!MO.getGlobal()->hasInternalLinkage());
|
|
|
|
} else {
|
|
|
|
Name.erase(Name.end()-5, Name.end());
|
|
|
|
StubSym =
|
|
|
|
MachineModuleInfoImpl::
|
|
|
|
StubValueTy(Ctx.GetOrCreateSymbol(Name.str()), false);
|
|
|
|
}
|
|
|
|
return Sym;
|
|
|
|
}
|
2010-11-15 03:13:19 +00:00
|
|
|
|
|
|
|
// If the symbol reference is actually to a non_lazy_ptr, not to the symbol,
|
|
|
|
// then add the suffix.
|
|
|
|
if (MO.getTargetFlags() & PPCII::MO_NLP_FLAG) {
|
|
|
|
Name += "$non_lazy_ptr";
|
|
|
|
MCSymbol *Sym = Ctx.GetOrCreateSymbol(Name.str());
|
|
|
|
|
|
|
|
MachineModuleInfoMachO &MachO = getMachOMMI(AP);
|
|
|
|
|
|
|
|
MachineModuleInfoImpl::StubValueTy &StubSym =
|
|
|
|
(MO.getTargetFlags() & PPCII::MO_NLP_HIDDEN_FLAG) ?
|
|
|
|
MachO.getHiddenGVStubEntry(Sym) : MachO.getGVStubEntry(Sym);
|
|
|
|
|
|
|
|
if (StubSym.getPointer() == 0) {
|
|
|
|
assert(MO.isGlobal() && "Extern symbol not handled yet");
|
|
|
|
StubSym = MachineModuleInfoImpl::
|
|
|
|
StubValueTy(AP.Mang->getSymbol(MO.getGlobal()),
|
|
|
|
!MO.getGlobal()->hasInternalLinkage());
|
|
|
|
}
|
|
|
|
return Sym;
|
2010-11-14 23:42:06 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
return Ctx.GetOrCreateSymbol(Name.str());
|
|
|
|
}
|
|
|
|
|
2010-11-14 21:20:46 +00:00
|
|
|
static MCOperand GetSymbolRef(const MachineOperand &MO, const MCSymbol *Symbol,
|
[PowerPC] Always use "assembler dialect" 1
A setting in MCAsmInfo defines the "assembler dialect" to use. This is used
by common code to choose between alternatives in a multi-alternative GNU
inline asm statement like the following:
__asm__ ("{sfe|subfe} %0,%1,%2" : "=r" (out) : "r" (in1), "r" (in2));
The meaning of these dialects is platform specific, and GCC defines those
for PowerPC to use dialect 0 for old-style (POWER) mnemonics and 1 for
new-style (PowerPC) mnemonics, like in the example above.
To be compatible with inline asm used with GCC, LLVM ought to do the same.
Specifically, this means we should always use assembler dialect 1 since
old-style mnemonics really aren't supported on any current platform.
However, the current LLVM back-end uses:
AssemblerDialect = 1; // New-Style mnemonics.
in PPCMCAsmInfoDarwin, and
AssemblerDialect = 0; // Old-Style mnemonics.
in PPCLinuxMCAsmInfo.
The Linux setting really isn't correct, we should be using new-style
mnemonics everywhere. This is changed by this commit.
Unfortunately, the setting of this variable is overloaded in the back-end
to decide whether or not we are on a Darwin target. This is done in
PPCInstPrinter (the "SyntaxVariant" is initialized from the MCAsmInfo
AssemblerDialect setting), and also in PPCMCExpr. Setting AssemblerDialect
to 1 for both Darwin and Linux no longer allows us to make this distinction.
Instead, this patch uses the MCSubtargetInfo passed to createPPCMCInstPrinter
to distinguish Darwin targets, and ignores the SyntaxVariant parameter.
As to PPCMCExpr, this patch adds an explicit isDarwin argument that needs
to be passed in by the caller when creating a target MCExpr. (To do so
this patch implicitly also reverts commit 184441.)
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@185858 91177308-0d34-0410-b5e6-96231b3b80d8
2013-07-08 20:20:51 +00:00
|
|
|
AsmPrinter &Printer, bool isDarwin) {
|
2010-11-14 21:20:46 +00:00
|
|
|
MCContext &Ctx = Printer.OutContext;
|
2010-11-14 23:42:06 +00:00
|
|
|
MCSymbolRefExpr::VariantKind RefKind = MCSymbolRefExpr::VK_None;
|
|
|
|
|
2012-06-04 17:36:38 +00:00
|
|
|
unsigned access = MO.getTargetFlags() & PPCII::MO_ACCESS_MASK;
|
|
|
|
|
2013-06-20 16:23:52 +00:00
|
|
|
switch (access) {
|
2013-06-21 14:42:20 +00:00
|
|
|
case PPCII::MO_TPREL_LO:
|
|
|
|
RefKind = MCSymbolRefExpr::VK_PPC_TPREL_LO;
|
2013-06-20 16:23:52 +00:00
|
|
|
break;
|
2013-06-21 14:42:20 +00:00
|
|
|
case PPCII::MO_TPREL_HA:
|
|
|
|
RefKind = MCSymbolRefExpr::VK_PPC_TPREL_HA;
|
2013-06-20 16:23:52 +00:00
|
|
|
break;
|
2013-06-21 14:42:20 +00:00
|
|
|
case PPCII::MO_DTPREL_LO:
|
|
|
|
RefKind = MCSymbolRefExpr::VK_PPC_DTPREL_LO;
|
2013-06-20 16:23:52 +00:00
|
|
|
break;
|
2013-06-21 14:42:20 +00:00
|
|
|
case PPCII::MO_TLSLD_LO:
|
|
|
|
RefKind = MCSymbolRefExpr::VK_PPC_GOT_TLSLD_LO;
|
2013-06-20 16:23:52 +00:00
|
|
|
break;
|
2013-06-21 14:42:20 +00:00
|
|
|
case PPCII::MO_TOC_LO:
|
|
|
|
RefKind = MCSymbolRefExpr::VK_PPC_TOC_LO;
|
2013-06-20 16:23:52 +00:00
|
|
|
break;
|
2013-07-05 12:22:36 +00:00
|
|
|
case PPCII::MO_TLS:
|
|
|
|
RefKind = MCSymbolRefExpr::VK_PPC_TLS;
|
|
|
|
break;
|
2013-05-23 22:26:41 +00:00
|
|
|
}
|
2010-11-14 23:42:06 +00:00
|
|
|
|
2010-11-15 03:13:19 +00:00
|
|
|
const MCExpr *Expr = MCSymbolRefExpr::Create(Symbol, RefKind, Ctx);
|
2010-11-14 23:42:06 +00:00
|
|
|
|
2010-11-14 21:20:46 +00:00
|
|
|
if (!MO.isJTI() && MO.getOffset())
|
|
|
|
Expr = MCBinaryExpr::CreateAdd(Expr,
|
|
|
|
MCConstantExpr::Create(MO.getOffset(), Ctx),
|
|
|
|
Ctx);
|
2010-11-15 02:46:57 +00:00
|
|
|
|
2010-11-15 03:13:19 +00:00
|
|
|
// Subtract off the PIC base if required.
|
|
|
|
if (MO.getTargetFlags() & PPCII::MO_PIC_FLAG) {
|
2010-11-15 02:46:57 +00:00
|
|
|
const MachineFunction *MF = MO.getParent()->getParent()->getParent();
|
|
|
|
|
|
|
|
const MCExpr *PB = MCSymbolRefExpr::Create(MF->getPICBaseSymbol(), Ctx);
|
|
|
|
Expr = MCBinaryExpr::CreateSub(Expr, PB, Ctx);
|
|
|
|
}
|
2013-05-23 22:26:41 +00:00
|
|
|
|
2013-06-20 16:23:52 +00:00
|
|
|
// Add ha16() / lo16() markers if required.
|
|
|
|
switch (access) {
|
2013-06-21 14:42:20 +00:00
|
|
|
case PPCII::MO_LO:
|
[PowerPC] Always use "assembler dialect" 1
A setting in MCAsmInfo defines the "assembler dialect" to use. This is used
by common code to choose between alternatives in a multi-alternative GNU
inline asm statement like the following:
__asm__ ("{sfe|subfe} %0,%1,%2" : "=r" (out) : "r" (in1), "r" (in2));
The meaning of these dialects is platform specific, and GCC defines those
for PowerPC to use dialect 0 for old-style (POWER) mnemonics and 1 for
new-style (PowerPC) mnemonics, like in the example above.
To be compatible with inline asm used with GCC, LLVM ought to do the same.
Specifically, this means we should always use assembler dialect 1 since
old-style mnemonics really aren't supported on any current platform.
However, the current LLVM back-end uses:
AssemblerDialect = 1; // New-Style mnemonics.
in PPCMCAsmInfoDarwin, and
AssemblerDialect = 0; // Old-Style mnemonics.
in PPCLinuxMCAsmInfo.
The Linux setting really isn't correct, we should be using new-style
mnemonics everywhere. This is changed by this commit.
Unfortunately, the setting of this variable is overloaded in the back-end
to decide whether or not we are on a Darwin target. This is done in
PPCInstPrinter (the "SyntaxVariant" is initialized from the MCAsmInfo
AssemblerDialect setting), and also in PPCMCExpr. Setting AssemblerDialect
to 1 for both Darwin and Linux no longer allows us to make this distinction.
Instead, this patch uses the MCSubtargetInfo passed to createPPCMCInstPrinter
to distinguish Darwin targets, and ignores the SyntaxVariant parameter.
As to PPCMCExpr, this patch adds an explicit isDarwin argument that needs
to be passed in by the caller when creating a target MCExpr. (To do so
this patch implicitly also reverts commit 184441.)
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@185858 91177308-0d34-0410-b5e6-96231b3b80d8
2013-07-08 20:20:51 +00:00
|
|
|
Expr = PPCMCExpr::CreateLo(Expr, isDarwin, Ctx);
|
2013-06-20 16:23:52 +00:00
|
|
|
break;
|
2013-06-21 14:42:20 +00:00
|
|
|
case PPCII::MO_HA:
|
[PowerPC] Always use "assembler dialect" 1
A setting in MCAsmInfo defines the "assembler dialect" to use. This is used
by common code to choose between alternatives in a multi-alternative GNU
inline asm statement like the following:
__asm__ ("{sfe|subfe} %0,%1,%2" : "=r" (out) : "r" (in1), "r" (in2));
The meaning of these dialects is platform specific, and GCC defines those
for PowerPC to use dialect 0 for old-style (POWER) mnemonics and 1 for
new-style (PowerPC) mnemonics, like in the example above.
To be compatible with inline asm used with GCC, LLVM ought to do the same.
Specifically, this means we should always use assembler dialect 1 since
old-style mnemonics really aren't supported on any current platform.
However, the current LLVM back-end uses:
AssemblerDialect = 1; // New-Style mnemonics.
in PPCMCAsmInfoDarwin, and
AssemblerDialect = 0; // Old-Style mnemonics.
in PPCLinuxMCAsmInfo.
The Linux setting really isn't correct, we should be using new-style
mnemonics everywhere. This is changed by this commit.
Unfortunately, the setting of this variable is overloaded in the back-end
to decide whether or not we are on a Darwin target. This is done in
PPCInstPrinter (the "SyntaxVariant" is initialized from the MCAsmInfo
AssemblerDialect setting), and also in PPCMCExpr. Setting AssemblerDialect
to 1 for both Darwin and Linux no longer allows us to make this distinction.
Instead, this patch uses the MCSubtargetInfo passed to createPPCMCInstPrinter
to distinguish Darwin targets, and ignores the SyntaxVariant parameter.
As to PPCMCExpr, this patch adds an explicit isDarwin argument that needs
to be passed in by the caller when creating a target MCExpr. (To do so
this patch implicitly also reverts commit 184441.)
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@185858 91177308-0d34-0410-b5e6-96231b3b80d8
2013-07-08 20:20:51 +00:00
|
|
|
Expr = PPCMCExpr::CreateHa(Expr, isDarwin, Ctx);
|
2013-06-20 16:23:52 +00:00
|
|
|
break;
|
2013-05-23 22:26:41 +00:00
|
|
|
}
|
|
|
|
|
2010-11-15 02:46:57 +00:00
|
|
|
return MCOperand::CreateExpr(Expr);
|
2010-11-14 21:20:46 +00:00
|
|
|
}
|
|
|
|
|
2010-11-14 21:12:33 +00:00
|
|
|
void llvm::LowerPPCMachineInstrToMCInst(const MachineInstr *MI, MCInst &OutMI,
|
[PowerPC] Always use "assembler dialect" 1
A setting in MCAsmInfo defines the "assembler dialect" to use. This is used
by common code to choose between alternatives in a multi-alternative GNU
inline asm statement like the following:
__asm__ ("{sfe|subfe} %0,%1,%2" : "=r" (out) : "r" (in1), "r" (in2));
The meaning of these dialects is platform specific, and GCC defines those
for PowerPC to use dialect 0 for old-style (POWER) mnemonics and 1 for
new-style (PowerPC) mnemonics, like in the example above.
To be compatible with inline asm used with GCC, LLVM ought to do the same.
Specifically, this means we should always use assembler dialect 1 since
old-style mnemonics really aren't supported on any current platform.
However, the current LLVM back-end uses:
AssemblerDialect = 1; // New-Style mnemonics.
in PPCMCAsmInfoDarwin, and
AssemblerDialect = 0; // Old-Style mnemonics.
in PPCLinuxMCAsmInfo.
The Linux setting really isn't correct, we should be using new-style
mnemonics everywhere. This is changed by this commit.
Unfortunately, the setting of this variable is overloaded in the back-end
to decide whether or not we are on a Darwin target. This is done in
PPCInstPrinter (the "SyntaxVariant" is initialized from the MCAsmInfo
AssemblerDialect setting), and also in PPCMCExpr. Setting AssemblerDialect
to 1 for both Darwin and Linux no longer allows us to make this distinction.
Instead, this patch uses the MCSubtargetInfo passed to createPPCMCInstPrinter
to distinguish Darwin targets, and ignores the SyntaxVariant parameter.
As to PPCMCExpr, this patch adds an explicit isDarwin argument that needs
to be passed in by the caller when creating a target MCExpr. (To do so
this patch implicitly also reverts commit 184441.)
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@185858 91177308-0d34-0410-b5e6-96231b3b80d8
2013-07-08 20:20:51 +00:00
|
|
|
AsmPrinter &AP, bool isDarwin) {
|
2010-11-14 19:53:02 +00:00
|
|
|
OutMI.setOpcode(MI->getOpcode());
|
|
|
|
|
|
|
|
for (unsigned i = 0, e = MI->getNumOperands(); i != e; ++i) {
|
|
|
|
const MachineOperand &MO = MI->getOperand(i);
|
|
|
|
|
|
|
|
MCOperand MCOp;
|
|
|
|
switch (MO.getType()) {
|
|
|
|
default:
|
|
|
|
MI->dump();
|
2012-02-07 02:50:20 +00:00
|
|
|
llvm_unreachable("unknown operand type");
|
2010-11-14 19:53:02 +00:00
|
|
|
case MachineOperand::MO_Register:
|
|
|
|
assert(!MO.getSubReg() && "Subregs should be eliminated!");
|
|
|
|
MCOp = MCOperand::CreateReg(MO.getReg());
|
|
|
|
break;
|
|
|
|
case MachineOperand::MO_Immediate:
|
|
|
|
MCOp = MCOperand::CreateImm(MO.getImm());
|
|
|
|
break;
|
2010-11-14 21:20:46 +00:00
|
|
|
case MachineOperand::MO_MachineBasicBlock:
|
|
|
|
MCOp = MCOperand::CreateExpr(MCSymbolRefExpr::Create(
|
|
|
|
MO.getMBB()->getSymbol(), AP.OutContext));
|
|
|
|
break;
|
|
|
|
case MachineOperand::MO_GlobalAddress:
|
|
|
|
case MachineOperand::MO_ExternalSymbol:
|
[PowerPC] Always use "assembler dialect" 1
A setting in MCAsmInfo defines the "assembler dialect" to use. This is used
by common code to choose between alternatives in a multi-alternative GNU
inline asm statement like the following:
__asm__ ("{sfe|subfe} %0,%1,%2" : "=r" (out) : "r" (in1), "r" (in2));
The meaning of these dialects is platform specific, and GCC defines those
for PowerPC to use dialect 0 for old-style (POWER) mnemonics and 1 for
new-style (PowerPC) mnemonics, like in the example above.
To be compatible with inline asm used with GCC, LLVM ought to do the same.
Specifically, this means we should always use assembler dialect 1 since
old-style mnemonics really aren't supported on any current platform.
However, the current LLVM back-end uses:
AssemblerDialect = 1; // New-Style mnemonics.
in PPCMCAsmInfoDarwin, and
AssemblerDialect = 0; // Old-Style mnemonics.
in PPCLinuxMCAsmInfo.
The Linux setting really isn't correct, we should be using new-style
mnemonics everywhere. This is changed by this commit.
Unfortunately, the setting of this variable is overloaded in the back-end
to decide whether or not we are on a Darwin target. This is done in
PPCInstPrinter (the "SyntaxVariant" is initialized from the MCAsmInfo
AssemblerDialect setting), and also in PPCMCExpr. Setting AssemblerDialect
to 1 for both Darwin and Linux no longer allows us to make this distinction.
Instead, this patch uses the MCSubtargetInfo passed to createPPCMCInstPrinter
to distinguish Darwin targets, and ignores the SyntaxVariant parameter.
As to PPCMCExpr, this patch adds an explicit isDarwin argument that needs
to be passed in by the caller when creating a target MCExpr. (To do so
this patch implicitly also reverts commit 184441.)
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@185858 91177308-0d34-0410-b5e6-96231b3b80d8
2013-07-08 20:20:51 +00:00
|
|
|
MCOp = GetSymbolRef(MO, GetSymbolFromOperand(MO, AP), AP, isDarwin);
|
2010-11-14 21:20:46 +00:00
|
|
|
break;
|
|
|
|
case MachineOperand::MO_JumpTableIndex:
|
[PowerPC] Always use "assembler dialect" 1
A setting in MCAsmInfo defines the "assembler dialect" to use. This is used
by common code to choose between alternatives in a multi-alternative GNU
inline asm statement like the following:
__asm__ ("{sfe|subfe} %0,%1,%2" : "=r" (out) : "r" (in1), "r" (in2));
The meaning of these dialects is platform specific, and GCC defines those
for PowerPC to use dialect 0 for old-style (POWER) mnemonics and 1 for
new-style (PowerPC) mnemonics, like in the example above.
To be compatible with inline asm used with GCC, LLVM ought to do the same.
Specifically, this means we should always use assembler dialect 1 since
old-style mnemonics really aren't supported on any current platform.
However, the current LLVM back-end uses:
AssemblerDialect = 1; // New-Style mnemonics.
in PPCMCAsmInfoDarwin, and
AssemblerDialect = 0; // Old-Style mnemonics.
in PPCLinuxMCAsmInfo.
The Linux setting really isn't correct, we should be using new-style
mnemonics everywhere. This is changed by this commit.
Unfortunately, the setting of this variable is overloaded in the back-end
to decide whether or not we are on a Darwin target. This is done in
PPCInstPrinter (the "SyntaxVariant" is initialized from the MCAsmInfo
AssemblerDialect setting), and also in PPCMCExpr. Setting AssemblerDialect
to 1 for both Darwin and Linux no longer allows us to make this distinction.
Instead, this patch uses the MCSubtargetInfo passed to createPPCMCInstPrinter
to distinguish Darwin targets, and ignores the SyntaxVariant parameter.
As to PPCMCExpr, this patch adds an explicit isDarwin argument that needs
to be passed in by the caller when creating a target MCExpr. (To do so
this patch implicitly also reverts commit 184441.)
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@185858 91177308-0d34-0410-b5e6-96231b3b80d8
2013-07-08 20:20:51 +00:00
|
|
|
MCOp = GetSymbolRef(MO, AP.GetJTISymbol(MO.getIndex()), AP, isDarwin);
|
2010-11-14 21:20:46 +00:00
|
|
|
break;
|
|
|
|
case MachineOperand::MO_ConstantPoolIndex:
|
[PowerPC] Always use "assembler dialect" 1
A setting in MCAsmInfo defines the "assembler dialect" to use. This is used
by common code to choose between alternatives in a multi-alternative GNU
inline asm statement like the following:
__asm__ ("{sfe|subfe} %0,%1,%2" : "=r" (out) : "r" (in1), "r" (in2));
The meaning of these dialects is platform specific, and GCC defines those
for PowerPC to use dialect 0 for old-style (POWER) mnemonics and 1 for
new-style (PowerPC) mnemonics, like in the example above.
To be compatible with inline asm used with GCC, LLVM ought to do the same.
Specifically, this means we should always use assembler dialect 1 since
old-style mnemonics really aren't supported on any current platform.
However, the current LLVM back-end uses:
AssemblerDialect = 1; // New-Style mnemonics.
in PPCMCAsmInfoDarwin, and
AssemblerDialect = 0; // Old-Style mnemonics.
in PPCLinuxMCAsmInfo.
The Linux setting really isn't correct, we should be using new-style
mnemonics everywhere. This is changed by this commit.
Unfortunately, the setting of this variable is overloaded in the back-end
to decide whether or not we are on a Darwin target. This is done in
PPCInstPrinter (the "SyntaxVariant" is initialized from the MCAsmInfo
AssemblerDialect setting), and also in PPCMCExpr. Setting AssemblerDialect
to 1 for both Darwin and Linux no longer allows us to make this distinction.
Instead, this patch uses the MCSubtargetInfo passed to createPPCMCInstPrinter
to distinguish Darwin targets, and ignores the SyntaxVariant parameter.
As to PPCMCExpr, this patch adds an explicit isDarwin argument that needs
to be passed in by the caller when creating a target MCExpr. (To do so
this patch implicitly also reverts commit 184441.)
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@185858 91177308-0d34-0410-b5e6-96231b3b80d8
2013-07-08 20:20:51 +00:00
|
|
|
MCOp = GetSymbolRef(MO, AP.GetCPISymbol(MO.getIndex()), AP, isDarwin);
|
2010-11-14 21:20:46 +00:00
|
|
|
break;
|
|
|
|
case MachineOperand::MO_BlockAddress:
|
[PowerPC] Always use "assembler dialect" 1
A setting in MCAsmInfo defines the "assembler dialect" to use. This is used
by common code to choose between alternatives in a multi-alternative GNU
inline asm statement like the following:
__asm__ ("{sfe|subfe} %0,%1,%2" : "=r" (out) : "r" (in1), "r" (in2));
The meaning of these dialects is platform specific, and GCC defines those
for PowerPC to use dialect 0 for old-style (POWER) mnemonics and 1 for
new-style (PowerPC) mnemonics, like in the example above.
To be compatible with inline asm used with GCC, LLVM ought to do the same.
Specifically, this means we should always use assembler dialect 1 since
old-style mnemonics really aren't supported on any current platform.
However, the current LLVM back-end uses:
AssemblerDialect = 1; // New-Style mnemonics.
in PPCMCAsmInfoDarwin, and
AssemblerDialect = 0; // Old-Style mnemonics.
in PPCLinuxMCAsmInfo.
The Linux setting really isn't correct, we should be using new-style
mnemonics everywhere. This is changed by this commit.
Unfortunately, the setting of this variable is overloaded in the back-end
to decide whether or not we are on a Darwin target. This is done in
PPCInstPrinter (the "SyntaxVariant" is initialized from the MCAsmInfo
AssemblerDialect setting), and also in PPCMCExpr. Setting AssemblerDialect
to 1 for both Darwin and Linux no longer allows us to make this distinction.
Instead, this patch uses the MCSubtargetInfo passed to createPPCMCInstPrinter
to distinguish Darwin targets, and ignores the SyntaxVariant parameter.
As to PPCMCExpr, this patch adds an explicit isDarwin argument that needs
to be passed in by the caller when creating a target MCExpr. (To do so
this patch implicitly also reverts commit 184441.)
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@185858 91177308-0d34-0410-b5e6-96231b3b80d8
2013-07-08 20:20:51 +00:00
|
|
|
MCOp = GetSymbolRef(MO,AP.GetBlockAddressSymbol(MO.getBlockAddress()),AP,
|
|
|
|
isDarwin);
|
2010-11-14 21:20:46 +00:00
|
|
|
break;
|
2012-01-18 23:52:19 +00:00
|
|
|
case MachineOperand::MO_RegisterMask:
|
|
|
|
continue;
|
2010-11-14 19:53:02 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
OutMI.addOperand(MCOp);
|
|
|
|
}
|
|
|
|
}
|