en Copyright 2015 Java http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/tools/llvm-profgen/Inputs/invalid-range.perfscript#9f732af5 [llvm-profgen] Filter out oversized LBR ranges.As a follow up to {D123271}, LBR ranges that are too big should also be considered as invalid.For example, the last two pairs in the following trace form a range [0x0d7b02b0, 0x368ba706] that covers a ton of functions in the binary. Such oversized range should also be ignored. 0x0c74505f/0x368b99a0 **0x368ba706**/0x0c745040 0x0d7b1c3f/**0x0d7b02b0**Add a defensive check to filter out those ranges based that the valid range should not cross the unconditional branch(Call, return, unconditional jmp).Reviewed By: hoy, wenleiDifferential Revision: https://reviews.llvm.org/D125448 List of files: /llvm-project-15.0.7/llvm/test/tools/llvm-profgen/Inputs/invalid-range.perfscript Thu, 12 May 2022 04:33:09 +0000 Hongtao Yu <hoy@fb.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/tools/llvm-profgen/Inputs/invalid-range.perfscript#8a0406dc [llvm-profgen] Filter out invalid LBR ranges.The profiler can sometimes give us a LBR trace that implicates bogus code ranges. For example, 0xc5acb56/0xc66c6c0 0xc628195/0xf31fbb0 0xc611261/0xc628130 0xc5c1a21/0xc6111c0 0x1f7edfd3/0xc5c3a50 0xc5c154f/0x1f7edec0 0xe8eed07/0xc5c11e0, note that the first two pairs are supposed to form a linear execution range, in this case, it is [0xf31fbb0, 0xc5acb56] , which doesn't make sense.Such bogus ranges should be ruled out to avoid generating a bad profile. I'm fixing this for both CS and non-CS cases.Reviewed By: wenleiDifferential Revision: https://reviews.llvm.org/D123271 List of files: /llvm-project-15.0.7/llvm/test/tools/llvm-profgen/Inputs/invalid-range.perfscript Fri, 08 Apr 2022 00:56:45 +0000 Hongtao Yu <hoy@fb.com>