mirror of
https://github.com/RPCS3/llvm.git
synced 2025-01-28 06:03:35 +00:00
Add computeFSAdditions to the function based subtarget creation
for PPC due to some unfortunate default setting via TargetMachine creation. I've added a FIXME on how this can be unraveled in the backend and a test to make sure we successfully legalize 64-bit things if we say we're 64-bits. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@233239 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
parent
6141f178a6
commit
3a77909dae
@ -207,7 +207,15 @@ PPCTargetMachine::getSubtargetImpl(const Function &F) const {
|
||||
// creation will depend on the TM and the code generation flags on the
|
||||
// function that reside in TargetOptions.
|
||||
resetTargetOptions(F);
|
||||
I = llvm::make_unique<PPCSubtarget>(TargetTriple, CPU, FS, *this);
|
||||
I = llvm::make_unique<PPCSubtarget>(
|
||||
TargetTriple, CPU,
|
||||
// FIXME: It would be good to have the subtarget additions here
|
||||
// not necessary. Anything that turns them on/off (overrides) ends
|
||||
// up being put at the end of the feature string, but the defaults
|
||||
// shouldn't require adding them. Fixing this means pulling Feature64Bit
|
||||
// out of most of the target cpus in the .td file and making it set only
|
||||
// as part of initialization via the TargetTriple.
|
||||
computeFSAdditions(FS, getOptLevel(), getTargetTriple()), *this);
|
||||
}
|
||||
return I.get();
|
||||
}
|
||||
|
Loading…
x
Reference in New Issue
Block a user