ARM and AArch64 SelectionDAG support for tacking parameter forwarding register is implemented so we can allow clang invocations for those two targets.
Beside that restrict debug entry value support to be emitted for LimitedDebugInfo info and FullDebugInfo. Other types of debug info do not have functions nor variables debug info.
Details
Diff Detail
Event Timeline
Update test/CodeGen/debug-info-param-modification.c?
lib/Frontend/CompilerInvocation.cpp | ||
---|---|---|
784 | This helper would be easier to read as an out-of-line function, imo. |
lib/Frontend/CompilerInvocation.cpp | ||
---|---|---|
784 | Or perhaps something like this? const llvm::Triple::ArchType DebugEntryValueArchs[] = {llvm::Triple::x86, [...]}; llvm::is_contained(DebugEntryValueArchs, Arch) |
lib/Frontend/CompilerInvocation.cpp | ||
---|---|---|
784 | I suppose this is fine, but it would be more elegant if we could query the target whether it supports entry values. |
lib/Frontend/CompilerInvocation.cpp | ||
---|---|---|
784 | At this point target has not been initialized yet. I considered adding such support to TargetMachine or LLVMTargetMachine but then we would need to reset this option later at some point when this object is initialized. |
This helper would be easier to read as an out-of-line function, imo.