diff options
author | Hal Finkel <hfinkel@anl.gov> | 2015-01-12 04:34:47 +0000 |
---|---|---|
committer | Hal Finkel <hfinkel@anl.gov> | 2015-01-12 04:34:47 +0000 |
commit | 87deb0b8e3f14855e6c4652993be86684c2dd429 (patch) | |
tree | 7d4f26d246de151733c6f5e38621c2684f1b1ed9 /clang/lib/Parse/ParseDecl.cpp | |
parent | 234b8188df4aa0c80d1beeb883f74ae9eb24d7ba (diff) | |
download | bcm5719-llvm-87deb0b8e3f14855e6c4652993be86684c2dd429.tar.gz bcm5719-llvm-87deb0b8e3f14855e6c4652993be86684c2dd429.zip |
[PowerPC] Fix calls to non-function objects
Looking at r225438 inspired me to see how the PowerPC backend handled the
situation (calling a bitcasted TLS global), and it turns out we also produced
an error (cannot select ...). What it means to "call" something that is not a
function is implementation and platform specific, but in the name of doing
something (besides crashing), this makes sure we do what GCC does (treat all
such calls as calls through a function pointer -- meaning that the pointer is
assumed, as is the convention on PPC, to point to a function descriptor
structure holding the actual code address along with the function's TOC pointer
and environment pointer). As GCC does, we now do the same for calling regular
(non-TLS) non-function globals too.
I'm not sure whether this is the most useful way to define the behavior, but at
least we won't be alone.
llvm-svn: 225617
Diffstat (limited to 'clang/lib/Parse/ParseDecl.cpp')
0 files changed, 0 insertions, 0 deletions