search for: d31898

Our ThinLTO testing was inoperative for a while, and now that it's running again, we're seeing the linker step reporting "Expected a single module." Note that our linker is using the C API to read bitcode. It looks like the ThinLTO writer now emits two modules, but AFAICT most of the APIs in BitcodeReader.cpp expect to see only one. Is this just an oversight in supporting

Hi Teresa, Thank you so much for your reply! I am on vacation until the end of this week and on EuroLLVM next week, so I have to apologize in advance that my replies are delayed. >>Right - see my reply on this from last night, at the very least the ThinLTO importing thresholds will need retuning if we will >>perform optimizations like unrolling/vectorization/etc that tend to

On Tue, Apr 10, 2018 at 11:52 PM, Mehdi AMINI <joker.eph at gmail.com> wrote: > > > Le mar. 10 avr. 2018 à 23:18, <katya.romanova at sony.com> a écrit : > >> Hi Mehdi, >> >> >> >> Awesome! It’s a very clear design. The only question left is which >> pipeline to choose for unified compile-phase optimization pipeline. >> >> -