2008-09-26 04:40:32 +00:00
|
|
|
set(LLVM_TARGET_DEFINITIONS X86.td)
|
2008-09-22 01:08:49 +00:00
|
|
|
|
2011-11-04 19:04:23 +00:00
|
|
|
tablegen(LLVM X86GenRegisterInfo.inc -gen-register-info)
|
|
|
|
|
tablegen(LLVM X86GenDisassemblerTables.inc -gen-disassembler)
|
|
|
|
|
tablegen(LLVM X86GenInstrInfo.inc -gen-instr-info)
|
|
|
|
|
tablegen(LLVM X86GenAsmWriter.inc -gen-asm-writer)
|
|
|
|
|
tablegen(LLVM X86GenAsmWriter1.inc -gen-asm-writer -asmwriternum=1)
|
|
|
|
|
tablegen(LLVM X86GenAsmMatcher.inc -gen-asm-matcher)
|
|
|
|
|
tablegen(LLVM X86GenDAGISel.inc -gen-dag-isel)
|
|
|
|
|
tablegen(LLVM X86GenFastISel.inc -gen-fast-isel)
|
|
|
|
|
tablegen(LLVM X86GenCallingConv.inc -gen-callingconv)
|
|
|
|
|
tablegen(LLVM X86GenSubtargetInfo.inc -gen-subtarget)
|
Clean up a pile of hacks in our CMake build relating to TableGen.
The first problem to fix is to stop creating synthetic *Table_gen
targets next to all of the LLVM libraries. These had no real effect as
CMake specifies that add_custom_command(OUTPUT ...) directives (what the
'tablegen(...)' stuff expands to) are implicitly added as dependencies
to all the rules in that CMakeLists.txt.
These synthetic rules started to cause problems as we started more and
more heavily using tablegen files from *subdirectories* of the one where
they were generated. Within those directories, the set of tablegen
outputs was still available and so these synthetic rules added them as
dependencies of those subdirectories. However, they were no longer
properly associated with the custom command to generate them. Most of
the time this "just worked" because something would get to the parent
directory first, and run tablegen there. Once run, the files existed and
the build proceeded happily. However, as more and more subdirectories
have started using this, the probability of this failing to happen has
increased. Recently with the MC refactorings, it became quite common for
me when touching a large enough number of targets.
To add insult to injury, several of the backends *tried* to fix this by
adding explicit dependencies back to the parent directory's tablegen
rules, but those dependencies didn't work as expected -- they weren't
forming a linear chain, they were adding another thread in the race.
This patch removes these synthetic rules completely, and adds a much
simpler function to declare explicitly that a collection of tablegen'ed
files are referenced by other libraries. From that, we can add explicit
dependencies from the smaller libraries (such as every architectures
Desc library) on this and correctly form a linear sequence. All of the
backends are updated to use it, sometimes replacing the existing attempt
at adding a dependency, sometimes adding a previously missing dependency
edge.
Please let me know if this causes any problems, but it fixes a rather
persistent and problematic source of build flakiness on our end.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@136023 91177308-0d34-0410-b5e6-96231b3b80d8
2011-07-26 00:09:08 +00:00
|
|
|
add_public_tablegen_target(X86CommonTableGen)
|
2008-09-22 01:08:49 +00:00
|
|
|
|
2009-08-12 15:54:28 +00:00
|
|
|
set(sources
|
2010-07-20 00:08:13 +00:00
|
|
|
X86AsmPrinter.cpp
|
|
|
|
|
X86CodeEmitter.cpp
|
|
|
|
|
X86FastISel.cpp
|
2008-09-22 01:08:49 +00:00
|
|
|
X86FloatingPoint.cpp
|
2011-01-10 12:39:23 +00:00
|
|
|
X86FrameLowering.cpp
|
2008-09-22 01:08:49 +00:00
|
|
|
X86ISelDAGToDAG.cpp
|
|
|
|
|
X86ISelLowering.cpp
|
|
|
|
|
X86InstrInfo.cpp
|
|
|
|
|
X86JITInfo.cpp
|
2010-07-20 00:08:13 +00:00
|
|
|
X86MCInstLower.cpp
|
2011-12-20 08:42:11 +00:00
|
|
|
X86MachineFunctionInfo.cpp
|
2013-01-08 18:27:24 +00:00
|
|
|
X86PadShortFunction.cpp
|
2008-09-22 01:08:49 +00:00
|
|
|
X86RegisterInfo.cpp
|
2010-07-20 00:08:13 +00:00
|
|
|
X86SelectionDAGInfo.cpp
|
2008-09-22 01:08:49 +00:00
|
|
|
X86Subtarget.cpp
|
|
|
|
|
X86TargetMachine.cpp
|
2009-09-16 04:44:00 +00:00
|
|
|
X86TargetObjectFile.cpp
|
Switch TargetTransformInfo from an immutable analysis pass that requires
a TargetMachine to construct (and thus isn't always available), to an
analysis group that supports layered implementations much like
AliasAnalysis does. This is a pretty massive change, with a few parts
that I was unable to easily separate (sorry), so I'll walk through it.
The first step of this conversion was to make TargetTransformInfo an
analysis group, and to sink the nonce implementations in
ScalarTargetTransformInfo and VectorTargetTranformInfo into
a NoTargetTransformInfo pass. This allows other passes to add a hard
requirement on TTI, and assume they will always get at least on
implementation.
The TargetTransformInfo analysis group leverages the delegation chaining
trick that AliasAnalysis uses, where the base class for the analysis
group delegates to the previous analysis *pass*, allowing all but tho
NoFoo analysis passes to only implement the parts of the interfaces they
support. It also introduces a new trick where each pass in the group
retains a pointer to the top-most pass that has been initialized. This
allows passes to implement one API in terms of another API and benefit
when some other pass above them in the stack has more precise results
for the second API.
The second step of this conversion is to create a pass that implements
the TargetTransformInfo analysis using the target-independent
abstractions in the code generator. This replaces the
ScalarTargetTransformImpl and VectorTargetTransformImpl classes in
lib/Target with a single pass in lib/CodeGen called
BasicTargetTransformInfo. This class actually provides most of the TTI
functionality, basing it upon the TargetLowering abstraction and other
information in the target independent code generator.
The third step of the conversion adds support to all TargetMachines to
register custom analysis passes. This allows building those passes with
access to TargetLowering or other target-specific classes, and it also
allows each target to customize the set of analysis passes desired in
the pass manager. The baseline LLVMTargetMachine implements this
interface to add the BasicTTI pass to the pass manager, and all of the
tools that want to support target-aware TTI passes call this routine on
whatever target machine they end up with to add the appropriate passes.
The fourth step of the conversion created target-specific TTI analysis
passes for the X86 and ARM backends. These passes contain the custom
logic that was previously in their extensions of the
ScalarTargetTransformInfo and VectorTargetTransformInfo interfaces.
I separated them into their own file, as now all of the interface bits
are private and they just expose a function to create the pass itself.
Then I extended these target machines to set up a custom set of analysis
passes, first adding BasicTTI as a fallback, and then adding their
customized TTI implementations.
The fourth step required logic that was shared between the target
independent layer and the specific targets to move to a different
interface, as they no longer derive from each other. As a consequence,
a helper functions were added to TargetLowering representing the common
logic needed both in the target implementation and the codegen
implementation of the TTI pass. While technically this is the only
change that could have been committed separately, it would have been
a nightmare to extract.
The final step of the conversion was just to delete all the old
boilerplate. This got rid of the ScalarTargetTransformInfo and
VectorTargetTransformInfo classes, all of the support in all of the
targets for producing instances of them, and all of the support in the
tools for manually constructing a pass based around them.
Now that TTI is a relatively normal analysis group, two things become
straightforward. First, we can sink it into lib/Analysis which is a more
natural layer for it to live. Second, clients of this interface can
depend on it *always* being available which will simplify their code and
behavior. These (and other) simplifications will follow in subsequent
commits, this one is clearly big enough.
Finally, I'm very aware that much of the comments and documentation
needs to be updated. As soon as I had this working, and plausibly well
commented, I wanted to get it committed and in front of the build bots.
I'll be doing a few passes over documentation later if it sticks.
Commits to update DragonEgg and Clang will be made presently.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@171681 91177308-0d34-0410-b5e6-96231b3b80d8
2013-01-07 01:37:14 +00:00
|
|
|
X86TargetTransformInfo.cpp
|
2011-08-23 01:14:17 +00:00
|
|
|
X86VZeroUpper.cpp
|
2013-04-25 20:29:37 +00:00
|
|
|
X86FixupLEAs.cpp
|
2008-09-22 01:08:49 +00:00
|
|
|
)
|
2009-07-02 18:53:52 +00:00
|
|
|
|
2009-08-14 19:56:04 +00:00
|
|
|
if( CMAKE_CL_64 )
|
2009-08-12 15:54:28 +00:00
|
|
|
enable_language(ASM_MASM)
|
2010-05-13 19:34:06 +00:00
|
|
|
ADD_CUSTOM_COMMAND(
|
|
|
|
|
OUTPUT ${CMAKE_CURRENT_BINARY_DIR}/X86CompilationCallback_Win64.obj
|
2010-11-16 22:07:47 +00:00
|
|
|
MAIN_DEPENDENCY X86CompilationCallback_Win64.asm
|
2010-05-13 19:34:06 +00:00
|
|
|
COMMAND ${CMAKE_ASM_MASM_COMPILER} /Fo ${CMAKE_CURRENT_BINARY_DIR}/X86CompilationCallback_Win64.obj /c ${CMAKE_CURRENT_SOURCE_DIR}/X86CompilationCallback_Win64.asm
|
|
|
|
|
)
|
2010-12-31 20:15:37 +00:00
|
|
|
set(sources ${sources} ${CMAKE_CURRENT_BINARY_DIR}/X86CompilationCallback_Win64.obj)
|
2009-08-12 15:54:28 +00:00
|
|
|
endif()
|
|
|
|
|
|
|
|
|
|
add_llvm_target(X86CodeGen ${sources})
|
2010-09-13 23:59:48 +00:00
|
|
|
|
2011-02-20 02:55:27 +00:00
|
|
|
add_subdirectory(AsmParser)
|
|
|
|
|
add_subdirectory(Disassembler)
|
|
|
|
|
add_subdirectory(InstPrinter)
|
2011-06-24 23:53:19 +00:00
|
|
|
add_subdirectory(MCTargetDesc)
|
2011-02-20 02:55:27 +00:00
|
|
|
add_subdirectory(TargetInfo)
|
|
|
|
|
add_subdirectory(Utils)
|
