Displaying 2 results from an estimated 2 matches for "mapmetadata".
2014 Dec 18
1
[LLVMdev] Metadata/Value split has landed
...ine 459.
>
> because we still have the temporary DISubprogram in there.
>
> Any ideas what to do about this?
>
The logic I have between `MapValue(Metadata*)` and `MapValueImpl(Metadata*)`
was supposed to solve this. (Actually, those names are awful, I may try to
change them to `MapMetadata()`.)
The logical flow should be:
- MapValue(Metadata*) calls MapValueImpl().
- MapValueImpl() introduces a temporary.
- MapValueImpl() recursively calls MapValueImpl().
- MapValueImpl() resolves its temporary.
- MapValue(Metadata*) calls resolveCycles().
There could be a bug here, but...
2014 Dec 10
4
[LLVMdev] Metadata/Value split has landed
The `Metadata`/`Value` split (PR21532) landed in r223802 -- at least, the
C++ side of it. This was a rocky day, but I suppose that's what I get
for failing to stage the change in smaller pieces.
As of r223916 (lldb), I'm not aware of any remaining (in-tree) breakage,
so if I've missed some problem in the sea of buildbot errors, please
flag me down.
I'll follow up soon with