Displaying 3 results from an estimated 3 matches for "9ff353fa".
2013 May 08
2
[LLVMdev] [lld] contentHash in the Reader ?
...tHash() const = 0
I'd use SHA128 or MD5 as the linker does not handle hostile input. I think
as long as it's collision free, it should suffice.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130509/9ff353fa/attachment.html>
2013 May 08
0
[LLVMdev] [lld] contentHash in the Reader ?
On 5/8/2013 12:38 AM, Michael Spencer wrote:
> On Tue, May 7, 2013 at 10:08 PM, Nick Kledzik <kledzik at apple.com> wrote:
>
>> Shankar,
>>
>> Do you mean add a method like:
>>
>> virtual unsigned contentHash() const = 0;
>>
>> or maybe:
>>
>> virtual llvm::hash_code contentHash() const = 0
We could use a crypto hash too
2013 May 08
4
[LLVMdev] [lld] contentHash in the Reader ?
On Tue, May 7, 2013 at 10:08 PM, Nick Kledzik <kledzik at apple.com> wrote:
> Shankar,
>
> Do you mean add a method like:
>
> virtual unsigned contentHash() const = 0;
>
> or maybe:
>
> virtual llvm::hash_code contentHash() const = 0
>
> to lld::DefinedAtom? That seems good to me. We just need to figure out
> what should happen with atoms not