File: iponly-nodupfactor.test

package info (click to toggle)
llvm-toolchain-19 1%3A19.1.7-3
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 1,998,520 kB
  • sloc: cpp: 6,951,680; ansic: 1,486,157; asm: 913,598; python: 232,024; f90: 80,126; objc: 75,281; lisp: 37,276; pascal: 16,990; sh: 10,009; ml: 5,058; perl: 4,724; awk: 3,523; makefile: 3,167; javascript: 2,504; xml: 892; fortran: 664; cs: 573
file content (22 lines) | stat: -rw-r--r-- 1,044 bytes parent folder | download | duplicates (3) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
 
; RUN: llvm-profgen --format=text --perfscript=%S/Inputs/ip-duplication.perfscript --binary=%S/Inputs/inline-noprobe2.perfbin --output=%t --use-offset=0 --leading-ip-only
; RUN: FileCheck %s --input-file %t --check-prefix=CHECK

; Test that we don't over-count samples for duplicated source code when
; building an IP-based profile.

; The inline-noprobe2.perfbin binary is used for this test because one of the
; partition_pivot_last+3.1 debug locations has a duplication factor of 2
; encoded into its discriminator. In IP-sample mode, a hit in one instruction
; in the duplicated code does not imply a hit to the other duplicates.

; The perfscript input includes 1 sample at a location with duplication factor
; of 2, and another sample at the same source location but with no duplication
; factor. These should be summed without duplication factors. Ensure we record
; a count of 1+1=2 (and not 2+1=3) for the 3.1 location.

;CHECK-LABEL: partition_pivot_last
;CHECK-NEXT:  1: 0
;CHECK-NEXT:  2: 0
;CHECK-NEXT:  3: 0
;CHECK-NEXT:  3.1: 2