I took a dump from LLDB and observed that many system frameworks and runtime libraries have a differently resolved target triple.
For example:
{
"path": "/Library/Developer/CoreSimulator/Volumes/iOS_22B81/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 18.1.simruntime/Contents/Resources/RuntimeRoot/usr/lib/system/libsystem_dnssd.dylib",
"triple": "arm64-apple-ios17.0.0-simulator"
},
{
"path": "/Applications/Xcode.16.1.0.16B40.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/Library/Frameworks/XCTest.framework/XCTest",
"triple": "arm64-apple-ios14.0.0-simulator",
},
{
"path": "/Library/Developer/CoreSimulator/Volumes/iOS_22B81/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 18.1.simruntime/Contents/Resources/RuntimeRoot/System/Library/PrivateFrameworks/USDLib_FormatLoaderProxy.framework/USDLib_FormatLoaderProxy",
"triple": "arm64-apple-ios16.0.0-simulator",
},
{
"path": "/Library/Developer/CoreSimulator/Volumes/iOS_22B81/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 18.1.simruntime/Contents/Resources/RuntimeRoot/usr/lib/system/libsystem_malloc.dylib",
"triple": "arm64-apple-ios18.1.0-simulator",
},
{
"path": "/Users/chirag.ramani/Library/Developer/Xcode/DerivedData/CoreA-gsgjjlpfoherfhbbwtokibblhlxw/Build/Intermediates.noindex/SwiftExplicitPrecompiledModules/Foundation-3DE7G7EH8SXDSTMRDGBAFZJFJ.pcm",
"triple": "arm64-apple-ios18.1.0-simulator"
}
I examined the .dylibs and frameworks (e.g., XCTest) and found that their target triple is influenced by the minOS version they are stamped with. The extra .pcms being generated appear to inherit the same triple.
Given this, could this mismatch be leading to .pcms generation on po?