search for: r300000

...a vendor publish toolchain #12 based on SVN r250000. - During subsequent LLVM development, changes happen (!). For example, a new key letter 'g' in the Data Layout. This is not a bitcode ambiguity so MODULE_CODE_VERSION is unchanged. - We as a vendor publish toolchain #13 based on SVN r300000. - Some middleware provider publishes libIncrediblyUseful.bc built using spiffy new toolchain #13. - Some hapless game developer tries to use libIncrediblyUseful.bc but is still on toolchain #12. This causes an error during some LTO build phase, of course; the question is, what kind of error...

...SVN r250000. > > - During subsequent LLVM development, changes happen (!). > > For example, a new key letter 'g' in the Data Layout. This is > > not a bitcode ambiguity so MODULE_CODE_VERSION is unchanged. > > - We as a vendor publish toolchain #13 based on SVN r300000. > > - Some middleware provider publishes libIncrediblyUseful.bc built > > using spiffy new toolchain #13. > > - Some hapless game developer tries to use libIncrediblyUseful.bc > > but is still on toolchain #12. This causes an error during some > > LTO build phas...

On Tue, Nov 4, 2014 at 9:10 PM, Bruce Hoult <bruce at hoult.org> wrote: > On Wed, Nov 5, 2014 at 2:30 PM, Sean Silva <chisophugis at gmail.com> wrote: > >> > Does Apple support library/middleware providers shipping bitcode instead >> >>> > of object code? >>> >>> No. >>> >> >> Are there ever any plans to do so?

...SVN r250000. > > - During subsequent LLVM development, changes happen (!). > > For example, a new key letter 'g' in the Data Layout. This is > > not a bitcode ambiguity so MODULE_CODE_VERSION is unchanged. > > - We as a vendor publish toolchain #13 based on SVN r300000. > > - Some middleware provider publishes libIncrediblyUseful.bc built > > using spiffy new toolchain #13. > > - Some hapless game developer tries to use libIncrediblyUseful.bc > > but is still on toolchain #12. This causes an error during some > > LTO build phas...