diff options
author | George Burgess IV <george.burgess.iv@gmail.com> | 2017-02-22 20:28:02 +0000 |
---|---|---|
committer | George Burgess IV <george.burgess.iv@gmail.com> | 2017-02-22 20:28:02 +0000 |
commit | f203dbfba9044987ea4af679ab697c1378c4fdaf (patch) | |
tree | 581875d6c98c86dabe45f663b4ea14958c975baf /lldb/packages/Python/lldbsuite/test/python_api/target/TestTargetAPI.py | |
parent | 8e6ee2070ad14c16ce80ee0b07839b96c3170d4a (diff) | |
download | bcm5719-llvm-f203dbfba9044987ea4af679ab697c1378c4fdaf.tar.gz bcm5719-llvm-f203dbfba9044987ea4af679ab697c1378c4fdaf.zip |
[CodeGen] Note where we add ABI-specific args in ctors. NFC.
Meta: The ultimate goal is to teach ExtParameterInfo about
pass_object_size attributes. This is necessary for that, since our
ExtParameterInfo is a bit buggy in C++. I plan to actually make use of
this Prefix/Suffix info in the near future, but I like small
single-purpose changes. Especially when those changes are hard to
actually test...
At the moment, some of our C++-specific CodeGen pretends that ABIs can
only add arguments to the beginning of a function call. This isn't quite
correct: args can be appended to the end, as well. It hasn't mattered
much until now, since we seem to only use this "number of arguments
added" data when calculating the ExtParameterInfo to use when making a
CGFunctionInfo. Said ExtParameterInfo is currently only used for
ParameterABIs (Swift) and ns_consumed (ObjC).
So, this patch allows ABIs to indicate whether args they added were at
the beginning or end of an argument list. We can use this information to
emit ExtParameterInfos more correctly, though like said, that bit is
coming soon.
No tests since this is theoretically a nop.
llvm-svn: 295870
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/target/TestTargetAPI.py')
0 files changed, 0 insertions, 0 deletions