search for: rl292517

...M? Merging sounds reasonbaly, I'd just like to understand what's the risk for the branch. On Thu, Jan 26, 2017 at 10:29 AM, Serge Rogatch <serge.rogatch at gmail.com> wrote: > Hans, these changes reached trunk in https://reviews.llvm.org/rL292516 and > https://reviews.llvm.org/rL292517 . Could you look? > > On 26 January 2017 at 03:29, Serge Rogatch <serge.rogatch at gmail.com> wrote: >> >> Sorry, I initially included LLVM-Commits rather than LLVM-Dev. Fixed. >> >> On 26 January 2017 at 03:26, Serge Rogatch <serge.rogatch at gmail.com> &g...

...'s the risk >> for the branch. >> >> On Thu, Jan 26, 2017 at 10:29 AM, Serge Rogatch <serge.rogatch at gmail.com> >> wrote: >> > Hans, these changes reached trunk in https://reviews.llvm.org/rL292516 >> > and >> > https://reviews.llvm.org/rL292517 . Could you look? >> > >> > On 26 January 2017 at 03:29, Serge Rogatch <serge.rogatch at gmail.com> >> > wrote: >> >> >> >> Sorry, I initially included LLVM-Commits rather than LLVM-Dev. Fixed. >> >> >> >> On 26 Januar...

Sorry, I initially included LLVM-Commits rather than LLVM-Dev. Fixed. On 26 January 2017 at 03:26, Serge Rogatch <serge.rogatch at gmail.com> wrote: > Hi Dean, Renato, > > AFAIK, unfortunately, these critical Arm32 XRay fixes are not yet in 4.0: > https://reviews.llvm.org/D28624 , https://reviews.llvm.org/D28623 . The > first repairs XRay instrumentation map emission.

...17 at 10:29 AM, Serge Rogatch >> >> <serge.rogatch at gmail.com> >> >> wrote: >> >> > Hans, these changes reached trunk in >> >> > https://reviews.llvm.org/rL292516 >> >> > and >> >> > https://reviews.llvm.org/rL292517 . Could you look? >> >> > >> >> > On 26 January 2017 at 03:29, Serge Rogatch <serge.rogatch at gmail.com> >> >> > wrote: >> >> >> >> >> >> Sorry, I initially included LLVM-Commits rather than LLVM-Dev. >> &...