Displaying 3 results from an estimated 3 matches for "locrecs".
2015 Sep 04
3
LLVM as a back end for HHVM
...t; attach to instructions? The general convention in LLVM is that
> dropping metadata should not affect correctness, and if the location
> record information is not best-effort or optional then metadata is
> perhaps not the best way to represent it.
Unfortunately not - all of our uses of locrecs are required for correctness.
>
> We're currently developing a scheme called "operand bundles" (more
> details at [1], patches at [2]) that can be used to tag calls and
> invokes with arbitrary values in a way that that they won't be dropped
> by the optimizer. Th...
2015 Sep 08
2
LLVM as a back end for HHVM
...onvention in LLVM is that
>>> dropping metadata should not affect correctness, and if the location
>>> record information is not best-effort or optional then metadata is
>>> perhaps not the best way to represent it.
>>
>> Unfortunately not - all of our uses of locrecs are required for
>> correctness.
>This will need to be a function attribute or operand bundle when
>upstreamed then, but that's a pretty simple change to make.
I think switching from metadata to operand bundles wouldn't be a problem,
assuming ³locrec² operand will have no effect...
2015 Sep 03
2
LLVM as a back end for HHVM
On 9/3/15, 3:34 PM, "Mehdi Amini" <mehdi.amini at apple.com<mailto:mehdi.amini at apple.com>> wrote:
Hi,
On Sep 3, 2015, at 1:38 PM, Maksim Panchenko via llvm-dev <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> wrote:
Hi All,
Our team at Hip-Hop Virtual Machine (http://hhvm.com<http://hhvm.com/>) have been experimenting with using LLVM