Displaying 7 results from an estimated 7 matches for "globalisneeded".
2015 May 19
2
[LLVMdev] Removing AvailableExternal values in GlobalDCE (was Re: RFC: ThinLTO Impementation Plan)
...unOnModule)
>>> >> already has a guard for !hasAvailableExternallyLinkage and
>>> >> !isDiscardableIfUnused, so my additional guard against marking
>>> >> imported functions is unnecessary. But the other place I had to change
>>> >> was in GlobalIsNeeded where it walks through the function and
>>> >> recursively marks any referenced global as needed. Here there was no
>>> >> guard against marking a global that is available externally as needed
>>> >> if it is referenced. I had added a check here to not m...
2015 May 19
2
[LLVMdev] Removing AvailableExternal values in GlobalDCE (was Re: RFC: ThinLTO Impementation Plan)
...!hasAvailableExternallyLinkage and
>> >>> >> !isDiscardableIfUnused, so my additional guard against marking
>> >>> >> imported functions is unnecessary. But the other place I had to
>> >>> >> change
>> >>> >> was in GlobalIsNeeded where it walks through the function and
>> >>> >> recursively marks any referenced global as needed. Here there was
>> >>> >> no
>> >>> >> guard against marking a global that is available externally as
>> >>> >> nee...
2015 Jun 04
2
[LLVMdev] Removing AvailableExternal values in GlobalDCE (was Re: RFC: ThinLTO Impementation Plan)
...gt;>>>>> !isDiscardableIfUnused, so my additional guard against marking
>>>>>>>>>>> imported functions is unnecessary. But the other place I had to
>>>>>>>>>>> change
>>>>>>>>>>> was in GlobalIsNeeded where it walks through the function and
>>>>>>>>>>> recursively marks any referenced global as needed. Here there
>>>>>>>>>>> was
>>>>>>>>>>> no
>>>>>>>>>>> guard agai...
2015 Jun 04
3
[LLVMdev] Removing AvailableExternal values in GlobalDCE (was Re: RFC: ThinLTO Impementation Plan)
...module to be removed with my changes.
>
> That's not what it looks like to me. Here's what I think the relevant
> part of your patch is:
>
> On 2015-May-18, at 21:09, Teresa Johnson <tejohnson at google.com> wrote:
>>
>> @@ -231,8 +237,10 @@ void GlobalDCE::GlobalIsNeeded(GlobalValue *G) {
>> for (Function::iterator BB = F->begin(), E = F->end(); BB != E; ++BB)
>> for (BasicBlock::iterator I = BB->begin(), E = BB->end(); I != E; ++I)
>> for (User::op_iterator U = I->op_begin(), E = I->op_end(); U != E; ++U)
>&...
2015 Jun 03
2
[LLVMdev] Removing AvailableExternal values in GlobalDCE (was Re: RFC: ThinLTO Impementation Plan)
...gt;> >> >>> >> !isDiscardableIfUnused, so my additional guard against marking
>> >> >>> >> imported functions is unnecessary. But the other place I had to
>> >> >>> >> change
>> >> >>> >> was in GlobalIsNeeded where it walks through the function and
>> >> >>> >> recursively marks any referenced global as needed. Here there
>> >> >>> >> was
>> >> >>> >> no
>> >> >>> >> guard against marking a global...
2015 May 15
2
[LLVMdev] RFC: ThinLTO Impementation Plan
On Fri, May 15, 2015 at 9:18 AM, David Blaikie <dblaikie at gmail.com> wrote:
>
>> >> - Marking of imported functions (for use in ThinLTO-specific symbol
>> >> linking and global DCE, for example).
>> >
>> > Marking how? Do you mean giving them internal linkage, or something
>> > else?
>>
>> Mentioned just after this: either
2015 May 15
3
[LLVMdev] RFC: ThinLTO Impementation Plan
...of the
> places I had changed (where we mark defined globals in runOnModule)
> already has a guard for !hasAvailableExternallyLinkage and
> !isDiscardableIfUnused, so my additional guard against marking
> imported functions is unnecessary. But the other place I had to change
> was in GlobalIsNeeded where it walks through the function and
> recursively marks any referenced global as needed. Here there was no
> guard against marking a global that is available externally as needed
> if it is referenced. I had added a check here to not mark imported
> functions as needed on reference...