summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/interpreter/main.c
diff options
context:
space:
mode:
authorSaleem Abdulrasool <compnerd@compnerd.org>2017-03-02 17:37:11 +0000
committerSaleem Abdulrasool <compnerd@compnerd.org>2017-03-02 17:37:11 +0000
commit97d25552ed0647f843dda92c47e3dd5bc4c6b90f (patch)
tree80047cb422a0da454cf3788ed212361cd74cdaba /lldb/packages/Python/lldbsuite/test/python_api/interpreter/main.c
parentfffa17983756af40fb726b425a314091767f1388 (diff)
downloadbcm5719-llvm-97d25552ed0647f843dda92c47e3dd5bc4c6b90f.tar.gz
bcm5719-llvm-97d25552ed0647f843dda92c47e3dd5bc4c6b90f.zip
Serialization: use the PCH chain to check PCH mode
When we are deciding whether we are creating a PCH or a module, we would check if the ModuleMgr had any elements to switch into PCH mode. However, when creating a module, the size may be 1. This would result in us going down the wrong path. This was found by cross-compiling the swift standard library. Use the PCH chain length instead to identify the PCH mode. Unfortunately, I have not yet been able to create a simple test case for this, but have verified that this fixes the swift standard library construction. Thanks to Adrian Prantl for help and discussions with this change! llvm-svn: 296769
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/interpreter/main.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud