Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(1186)

Issue 151051: [PATCH] Make the need-stub variables accurate and consistent (Closed)

Can't Edit
Can't Publish+Mail
Start Review
Created:
15 years, 1 month ago by Jeffrey Yasskin
Modified:
15 years, 1 month ago
Reviewers:
CC:
llvm-commits_cs.uiuc.edu
Visibility:
Public.

Description

I'm trying to tease apart the different uses for "stubs" in the JIT. In the case of MachineRelocations, I believe "stub" always refers to a far-call stub or a load-a-faraway-global stub, so this patch adds "Far" to the term. 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.

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+49 lines, -48 lines) Patch
M include/llvm/CodeGen/MachineRelocation.h View 10 chunks +17 lines, -15 lines 0 comments Download
M lib/ExecutionEngine/JIT/JITEmitter.cpp View 7 chunks +13 lines, -15 lines 0 comments Download
M lib/Target/ARM/ARMCodeEmitter.cpp View 2 chunks +5 lines, -4 lines 0 comments Download
M lib/Target/X86/X86CodeEmitter.cpp View 8 chunks +14 lines, -14 lines 0 comments Download

Messages

Total messages: 1
Jeffrey Yasskin
15 years, 1 month ago (2009-11-07 05:30:10 UTC) #1
Please take a look.

I'd like to find an example of a global-variable far stub to put in the comment
for MachineRelocation::mayNeedFarStub(). Can anyone describe the requirement for
ARM or another platform so I can copy it in?
Sign in to reply to this message.

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld f62528b