6329355860
We have a textual representation of contextual profiles for test scenarios, mainly. This patch moves that to YAML instead of JSON. YAML is more succinct and readable (some of the .ll tests should be illustrative). In addition, JSON is parse-able by the YAML reader. A subsequent patch will address deserialization. (thanks, @kazutakahirata, for showing me how to use the llvm YAML reader/writer APIs, which I incorrectly thought to be more low-level than the JSON ones!)
44 lines
1.2 KiB
LLVM
44 lines
1.2 KiB
LLVM
; REQUIRES: x86_64-linux
|
|
;
|
|
; Check that, if none of the roots in the profile are defined in the module, the
|
|
; profile is treated as empty (i.e. "none provided")
|
|
;
|
|
; RUN: rm -rf %t
|
|
; RUN: split-file %s %t
|
|
; RUN: llvm-ctxprof-util fromYAML --input=%t/profile.yaml --output=%t/profile.ctxprofdata
|
|
; RUN: opt -passes='require<ctx-prof-analysis>,print<ctx-prof-analysis>' -ctx-profile-printer-level=everything \
|
|
; RUN: %t/example.ll -S 2>&1 | FileCheck %s
|
|
|
|
; CHECK: No contextual profile was provided
|
|
;
|
|
; This is the reference profile, laid out in the format the json formatter will
|
|
; output it from opt. Note that the root GUIDs - 12341 and 34234 - are different from
|
|
; the GUID present in the module, which is otherwise present in the profile, but not
|
|
; as a root.
|
|
;--- profile.yaml
|
|
- Guid: 12341
|
|
Counters: [9]
|
|
- Guid: 1000
|
|
Counters: [5]
|
|
- Guid: 34234
|
|
Counters: [1]
|
|
Callsites: -
|
|
- Guid: 1000
|
|
Counters: [6, 7]
|
|
;--- example.ll
|
|
declare void @bar()
|
|
|
|
define void @an_entrypoint(i32 %a) !guid !0 {
|
|
%t = icmp eq i32 %a, 0
|
|
br i1 %t, label %yes, label %no
|
|
|
|
yes:
|
|
call void @bar()
|
|
ret void
|
|
no:
|
|
ret void
|
|
}
|
|
|
|
attributes #0 = { noinline }
|
|
!0 = !{ i64 1000 }
|