llvm-project/llvm/test/Analysis/CallGraph/2008-09-09-DirectCall.ll

; RUN: llvm-as < %s | opt -print-callgraph -disable-output |& \
; RUN:   grep {Calls function 'callee'} | count 2

define internal void @callee(...) {
entry:
	unreachable
}

define void @caller() {
entry:
	call void (...)* @callee( void (...)* @callee )
	unreachable
}
Rationalize the names of passes that print information: -callgraph => print-callgraph -callscc => print-callgraph-sccs -cfgscc => print-cfg-sccs -externalfnconstants => print-externalfnconstants -print => print-function -print-alias-sets (no change) -print-callgraph => dot-callgraph -print-cfg => dot-cfg -print-cfg-only => dot-cfg-only -print-dom-info (no change) -printm => print-module -printusedtypes => print-used-types llvm-svn: 56487 2008-09-23 20:47:39 +08:00			`; RUN: llvm-as < %s \| opt -print-callgraph -disable-output \|& \`
			`; RUN: grep {Calls function 'callee'} \| count 2`
Correct callgraph construction. It has two problems: (1) code left over from the days of ConstantPointerRef: if a use of a function is a GlobalValue then that is not considered a reason to add an edge from the external node, even though the use may be as an initializer for an externally visible global! There might be some point to this behaviour when the use is by an alias (though the code predated aliases by some centuries), but I think PR2782 is a better way of handling that. (2) If function F calls function G, and also G is a parameter to the call, then an F->G edge is not added to the callgraph. While this doesn't seem to matter much, adding such an edge makes the callgraph more regular. In addition, the new code should be faster as well as simpler. llvm-svn: 55987 2008-09-09 20:40:47 +08:00
			`define internal void @callee(...) {`
			`entry:`
			`unreachable`
			`}`

			`define void @caller() {`
			`entry:`
			`call void (...)* @callee( void (...)* @callee )`
			`unreachable`
			`}`