summaryrefslogtreecommitdiffstats
path: root/lldb/source/Plugins/Process/Linux/ProcessMonitor.cpp
diff options
context:
space:
mode:
authorJohn McCall <rjmccall@apple.com>2014-02-27 20:30:49 +0000
committerJohn McCall <rjmccall@apple.com>2014-02-27 20:30:49 +0000
commit95833f33bda6c92e746e0b0007b69c2c30bfc693 (patch)
tree3f0dd01a6f42e90cd650d1d1be1e4c0bf8e9d1fe /lldb/source/Plugins/Process/Linux/ProcessMonitor.cpp
parentd6efa2a9775790b8662393a9f9634516b647e091 (diff)
downloadbcm5719-llvm-95833f33bda6c92e746e0b0007b69c2c30bfc693.tar.gz
bcm5719-llvm-95833f33bda6c92e746e0b0007b69c2c30bfc693.zip
Diagnose attempts to apply ms_struct to records with base classes
or virtual functions, but permit that error to be downgraded to a warning (with -Wno-error=incompatible-ms-struct), and officially support this kind of dual, ABI-mixing layout. The basic problem here is that projects which use ms_struct are often not very circumspect about what types they annotate; for example, some projects enable the pragma in a prefix header and then only selectively disable it around system header inclusions. They may only care about binary compatibility with MSVC for a subset of those structs, but that doesn't mean they have no binary compatibility concerns at all for the rest; thus we are essentially forced into supporting this hybrid ABI. But it's reasonable for us to at least point out the places where we're not making any guarantees. The original diagnostic was for dynamic classes, i.e. those with virtual functions or virtual bases; I've extended it to include all classes with bases, because we are not actually making any attempt to duplicate MSVC's base subobject layout in ms_struct (and it is indeed quite different from Itanium, even for non-virtual bases). rdar://16178895 llvm-svn: 202427
Diffstat (limited to 'lldb/source/Plugins/Process/Linux/ProcessMonitor.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud