Displaying 3 results from an estimated 3 matches for "isproto".
2016 Apr 20
2
Lazily Loaded Modules and Linker::LinkOnlyNeeded
>
>
> I understood from his description that he reversed the destination and
> source so that destination is the user code.
> I assumed it was not lazy loaded, but that would explain the question then
> :)
>
> Neil: can you clarify? If Teresa is right, why aren't you materializing
> the destination module entirely?
>
>
I don't think it has ever been tried
2017 Apr 04
3
RFC: Adding a string table to the bitcode format
On Tue, Apr 4, 2017 at 12:36 PM, Duncan P. N. Exon Smith <
dexonsmith at apple.com> wrote:
>
> On 2017-Apr-04, at 12:12, Peter Collingbourne <peter at pcc.me.uk> wrote:
>
> On Mon, Apr 3, 2017 at 8:13 PM, Mehdi Amini <mehdi.amini at apple.com> wrote:
>
>>
>> On Apr 3, 2017, at 7:08 PM, Peter Collingbourne <peter at pcc.me.uk> wrote:
>>
2016 Apr 21
4
Lazily Loaded Modules and Linker::LinkOnlyNeeded
...said that, I don't think isMaterializable should return
> true for a declaration.
>
>
> Looking at isMaterializable, I'm now a little confused about Neil's
> case - the materializable bit is set to true only when
> the MODULE_CODE_FUNCTION indicated that it was !isproto, which means
> it should have a definition in that module. So I agree with you that
> isMaterializable shouldn't be returning true when the symbol is only
> available as a declaration.
>
> Neil - what case are you trying to handle here? If there is a
> materializable defin...