search for: xcode9

...rformance when upgrading > (I think TBAA comes to my mind right now, but other kind of metadata have > also been lost). Now every case is different, and the FMF can be considered > too important to be left on the table. > For example it would impact LTO when loading libraries built with Xcode9 > and before whenever the next released post-r317488 come up. > > > >> I know this performance drop is not acceptable for our use cases, but I >> don’t want to impose our ruling on this. >> >> >> What about any bitcode shipped after r317488 but before the v...

...reserving all the performance when upgrading (I think TBAA comes to my mind right now, but other kind of metadata have also been lost). Now every case is different, and the FMF can be considered too important to be left on the table. For example it would impact LTO when loading libraries built with Xcode9 and before whenever the next released post-r317488 come up. > I know this performance drop is not acceptable for our use cases, but I > don’t want to impose our ruling on this. > > > What about any bitcode shipped after r317488 but before the version bump? > Not worth taking in...

...pgrading >> (I think TBAA comes to my mind right now, but other kind of metadata have >> also been lost). Now every case is different, and the FMF can be considered >> too important to be left on the table. >> For example it would impact LTO when loading libraries built with Xcode9 >> and before whenever the next released post-r317488 come up. >> >> >> >>> I know this performance drop is not acceptable for our use cases, but I >>> don’t want to impose our ruling on this. >>> >>> >>> What about any bitcode sh...

Hi Mehdi, > On Feb 13, 2018, at 12:34 PM, Mehdi AMINI <joker.eph at gmail.com> wrote: > > > > 2018-02-08 17:34 GMT-08:00 Quentin Colombet via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>>: > Hi, > > TL;DR > r317488 changed the way fast math flags are laid out in the bitcode and anyone compiling a pre-llvm-6.0 bitcode