summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Analysis/AliasSetTracker.cpp
diff options
context:
space:
mode:
authorAleksei Sidorin <a.sidorin@samsung.com>2018-10-29 21:46:18 +0000
committerAleksei Sidorin <a.sidorin@samsung.com>2018-10-29 21:46:18 +0000
commit89c1ac7a05c16e67ac89027ed39a7211b2b3a663 (patch)
treeec2a0eb4bf9b98a56ec62b6649ddb5732cc21710 /llvm/lib/Analysis/AliasSetTracker.cpp
parentf4e75a500517504e6e90db836a9e31ce2717a5aa (diff)
downloadbcm5719-llvm-89c1ac7a05c16e67ac89027ed39a7211b2b3a663.tar.gz
bcm5719-llvm-89c1ac7a05c16e67ac89027ed39a7211b2b3a663.zip
[ASTImporter] Reorder fields after structure import is finished
There are multiple reasons why field structures can be imported in wrong order. The simplest is the ability of field initializers and method bodies to refer fields not in order they are listed in. Unfortunately, there is no clean solution for that currently so I'm leaving a FIXME. Differential Revision: https://reviews.llvm.org/D44100 llvm-svn: 345545
Diffstat (limited to 'llvm/lib/Analysis/AliasSetTracker.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud