In particular this affects how target create --arch is handled — it allowed us to override the deployment target (a useful feature for the expression evaluator), but the fat binary case didn't.
rdar://problem/66024437
Paths
| Differential D85049
Unify the code that updates the ArchSpec after finding a fat binary with how it is done for a lean binary ClosedPublic Authored by aprantl on Jul 31 2020, 2:59 PM.
Details Summary In particular this affects how target create --arch is handled — it allowed us to override the deployment target (a useful feature for the expression evaluator), but the fat binary case didn't. rdar://problem/66024437
Diff Detail
Event TimelineComment Actions It would be nice to (in a follow-up-patch) clearly state what this function's goal is and then re-implement it with slightly fewer fallbacks. The code as it is is very convoluted.
Comment Actions LGTM, it's hard to keep all the supported behaviors in my head but I think this is right. This revision is now accepted and ready to land.Aug 6 2020, 1:15 PM Closed by commit rG0fa520af6734: Unify the code that updates the ArchSpec after finding a fat binary (authored by aprantl). · Explain WhyAug 6 2020, 1:30 PM This revision was automatically updated to reflect the committed changes.
Revision Contents
Diff 283719 lldb/source/Target/TargetList.cpp
lldb/test/API/macosx/universal/Makefile
lldb/test/API/macosx/universal/TestUniversal.py
|
Is this check strict enough? I thought it should be only TripleOSWasSpecified -- what we can infer from the vendor?