diff options
| author | Bill Wendling <isanbard@gmail.com> | 2009-11-18 01:03:56 +0000 |
|---|---|---|
| committer | Bill Wendling <isanbard@gmail.com> | 2009-11-18 01:03:56 +0000 |
| commit | c3bd9875c4cffb6514b54839c0220cfeccb5b7a9 (patch) | |
| tree | 642ec53ac5486505dbc7587657803d280d8f488b /lib/ExecutionEngine/Interpreter/ExternalFunctions.cpp | |
| parent | 10fd2878665f7ae15848e0d5166a5ea873e2bac8 (diff) | |
| download | external_llvm-c3bd9875c4cffb6514b54839c0220cfeccb5b7a9.tar.gz external_llvm-c3bd9875c4cffb6514b54839c0220cfeccb5b7a9.tar.bz2 external_llvm-c3bd9875c4cffb6514b54839c0220cfeccb5b7a9.zip | |
The llvm-gcc front-end and the pass manager use two separate TargetData objects.
This is probably not confined to *just* these two things.
Anyway, the llvm-gcc front-end may look up the structure layout information for
an abstract type. That information will be stored into a table with the FE's
TD. Instruction combine can come along and also ask for information on that
abstract type, but for a separate TD (the one associated with the pass manager).
After the type is refined, the old structure layout information in the pass
manager's TD file is out of date. If a new type is allocated in the same space
as the old-unrefined type, then the structure type information in the pass
manager's TD file will be wrong, but won't know it.
Fix this by making the TD's structure type information an abstract type user.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@89176 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'lib/ExecutionEngine/Interpreter/ExternalFunctions.cpp')
0 files changed, 0 insertions, 0 deletions