Make the need-stub variables accurate and consistent. In the case of
authorJeffrey Yasskin <jyasskin@google.com>
Sat, 7 Nov 2009 08:51:52 +0000 (08:51 +0000)
committerJeffrey Yasskin <jyasskin@google.com>
Sat, 7 Nov 2009 08:51:52 +0000 (08:51 +0000)
commit2d274412ed9aab277e070690c574714ec544cf94
tree44f78ccda7c080daea2f0c34082468671f9bb7b8
parent761411c21b27c5a7fd2368f0a35d312013f2b5c5
Make the need-stub variables accurate and consistent.  In the case of
MachineRelocations, "stub" always refers to a far-call stub or a
load-a-faraway-global stub, so this patch adds "Far" to the term. (Other stubs
are used for lazy compilation and dlsym address replacement.) The variable was
also inconsistent between the positive and negative sense, and the positive
sense ("NeedStub") was more demanding than is accurate (since a nearby-enough
function can be called directly even if the platform often requires a stub).
Since the negative sense causes double-negatives, I switched to
"MayNeedFarStub" globally.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@86363 91177308-0d34-0410-b5e6-96231b3b80d8
include/llvm/CodeGen/MachineRelocation.h
lib/ExecutionEngine/JIT/JITEmitter.cpp
lib/Target/ARM/ARMCodeEmitter.cpp
lib/Target/X86/X86CodeEmitter.cpp