search for: r226095

...; >>>> I suspect it would actually be *better* if I got all this in before >>>> the branch, since it'll make cherry-picking testcases easier. >>> >>> Excellent point, go for it. >> >> I missed the branch deadline, but I merged it in as of r226095. > > Thanks! Can you prepare an update to the release notes that cover the > debug info / metadata changes? How does this look? -------------- next part -------------- A non-text attachment was scrubbed... Name: metadata-3.6.patch Type: application/octet-stream Size: 5445 bytes Desc: no...

...ul_Robinson at playstation.sony.com> wrote: > >> I suspect it would actually be *better* if I got all this in before >> the branch, since it'll make cherry-picking testcases easier. > > Excellent point, go for it. I missed the branch deadline, but I merged it in as of r226095. > --paulr > >> >> However, these patches themselves (and I suspect a few more prep >> commits) don't actually move `MDLocation` into place -- it's not >> until then that all the testcase updates have to happen. I'm not >> convinced that (monster)...

I just finished the work for PR21433. I think it's relatively low risk, but it does change assembly output. Should I commit this before or after the (imminent) 3.6 branch? (I would have committed it tonight, but the buildbots are fairly red, and I prefer to break out-of-tree code in the morning anyway.) -------------- next part -------------- A non-text attachment was scrubbed... Name:

I suspect it would actually be *better* if I got all this in before the branch, since it'll make cherry-picking testcases easier. However, these patches themselves (and I suspect a few more prep commits) don't actually move `MDLocation` into place -- it's not until then that all the testcase updates have to happen. I'm not convinced that (monster) commit will land by tomorrow :(.