================ @@ -0,0 +1,63 @@ +// For an 'inline' function with multiple definitions in different +// translation units (TUs), its call sites in different TUs and one of +// its definitions, which is chosen by the linker, are properly connected +// during bounds propagation. + + +// RUN: rm -rf %t +// RUN: mkdir -p %t +// RUN: split-file %s %t + +// Extract per-TU PointerFlow + UnsafeBufferUsage summaries. +// RUN: %clang_cc1 -fsyntax-only -I %t %t/tu1.cpp \ +// RUN: --ssaf-extract-summaries=PointerFlow \ +// RUN: --ssaf-extract-summaries=UnsafeBufferUsage \ +// RUN: --ssaf-tu-summary-file=%t/tu1.summary.json +// RUN: %clang_cc1 -fsyntax-only -I %t %t/tu2.cpp \ +// RUN: --ssaf-extract-summaries=PointerFlow \ +// RUN: --ssaf-extract-summaries=UnsafeBufferUsage \ +// RUN: --ssaf-tu-summary-file=%t/tu2.summary.json ---------------- ziqingluo-90 wrote:
yep, that makes the test easier to read. https://github.com/llvm/llvm-project/pull/201946 _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
