Displaying 2 results from an estimated 2 matches for "mdnodefwdref".
2014 Nov 10
5
[LLVMdev] [RFC] Separating Metadata from the Value hierarchy
...ch -- it should use `TrackingMDRef`. When
the forward reference gets resolved, it updates all of its tracking
references.
Nevertheless, `sizeof(MDRef) == sizeof(TrackingMDRef) == sizeof(void*)`.
Frontends *only* pay memory overhead for the currently-unresolved
forward references.
(Maybe `MDNodeFwdRef` is a better name than `TempMDNode`?)
>
>> 2. No more function-local metadata.
>
> This was a great idea that never mattered, I’m happy to drop it for the greater good :-)
>
Awesome.
> +class Metadata {
> +private:
> + LLVMContext &Context;
>
> Out of cu...
2014 Nov 10
12
[LLVMdev] [RFC] Separating Metadata from the Value hierarchy
TL;DR: If you use metadata (especially if it's out-of-tree), check the
numbered list of lost functionality below to see whether I'm trying to
break your compiler permanently.
In response to my recent commits (e.g., [1]) that changed API from
`MDNode` to `Value`, Eric had a really interesting idea [2] -- split
metadata entirely from the `Value` hierarchy, and drop general support
for