diff options
| author | Jason Molenda <jmolenda@apple.com> | 2018-01-12 01:16:13 +0000 |
|---|---|---|
| committer | Jason Molenda <jmolenda@apple.com> | 2018-01-12 01:16:13 +0000 |
| commit | c4dd04c5c3077b311532d61fda256590aa96ee0c (patch) | |
| tree | ea6a48ea81c1af74a12d36a9685d26a09bc6f9fd /lldb/packages/Python/lldbsuite/test/lang/cpp | |
| parent | e38b018df4c4524cda9f61cedfe5a8ab551c6e93 (diff) | |
| download | bcm5719-llvm-c4dd04c5c3077b311532d61fda256590aa96ee0c.tar.gz bcm5719-llvm-c4dd04c5c3077b311532d61fda256590aa96ee0c.zip | |
When parsing the target.xml register file, if no architecture has
been specified yet (either by the user, or by one of the lldb
extensions like qHostInfo or qProcessInfo), and the target.xml
includes a <architecture> tag specifying x86_64, set the architecture
appropriately.
I'm not sure what we can expect to see in the <architecture> tag, so
I'm only doing this for x86_64 right now where I've seen "i386:x86_64"
used. I've seen a target.xml from a jtag board that sends just "arm"
because it doesn't know more specifically what type of board it is
connected to...
<rdar://problem/29908970>
llvm-svn: 322339
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/lang/cpp')
0 files changed, 0 insertions, 0 deletions
