From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 2002:ac8:5215:: with SMTP id r21-v6mr4269802qtn.55.1527185221643; Thu, 24 May 2018 11:07:01 -0700 (PDT) X-Received: by 2002:a1f:2cd1:: with SMTP id s200-v6mr1247493vks.14.1527185221531; Thu, 24 May 2018 11:07:01 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!news.uzoreto.com!weretis.net!feeder6.news.weretis.net!feeder.usenetexpress.com!feeder-in1.iad1.usenetexpress.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!x25-v6no969198qto.0!news-out.google.com!p41-v6ni286qtp.1!nntp.google.com!x25-v6no969195qto.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Thu, 24 May 2018 11:07:01 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=2a02:c7d:3c35:b000:325a:3aff:fe0f:37a5; posting-account=L2-UcQkAAAAfd_BqbeNHs3XeM0jTXloS NNTP-Posting-Host: 2a02:c7d:3c35:b000:325a:3aff:fe0f:37a5 References: <5c2523c1-9ea5-453c-b80e-9cb0dcd16de0@googlegroups.com> <293cf892-1320-49e6-a25f-a36ea098cd34@googlegroups.com> <294fa0cd-ec72-4f0f-8065-0a3d5e1087fa@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <1758ba60-2171-4967-bc75-6176f9f18ec1@googlegroups.com> Subject: Re: DragonEgg has been revived From: Lucretia Injection-Date: Thu, 24 May 2018 18:07:01 +0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Xref: reader02.eternal-september.org comp.lang.ada:52645 Date: 2018-05-24T11:07:01-07:00 List-Id: On Thursday, 24 May 2018 17:44:22 UTC+1, Dan'l Miller wrote: > Oh great. Now I have convinced myself that there is enough sketchiness/d= odginess in this vicinity to question whether Apple's forthcoming App-Store= LLVM-bitcode-IR recompiler wouldn't satisfy any one or more required terms= of any GPLv3-with-RLEv3.1-licensed compiler (FSF or otherwise) in such as = way as to cause both: > 1) the app to need to provide its Source Code; > and > 2) Apple to need to provide the Installation Information and Correspondin= g Source Code on a =E2=80=9Cconsumer=E2=80=9D device that is not-=E2=80=9Cs= ufficiently=E2=80=9D =E2=80=9Cindustrial=E2=80=9D, where that consumer devi= ce (e.g., an Apple iDevice) might be a User Product in the terms of GPLv3. > and thus > 3) merely compiling the app with GPLv3-with-RLEv3.1-licensed compiler (an= d the app invoking at least one subroutine in the RLEv3.1-licensed runtime)= could conceivably be enough for Apple to reject such apps from the App Sto= re, so that Apple need not satisfy #2 above. >=20 > https://thenextweb.com/apple/2015/06/17/apples-biggest-developer-news-at-= wwdc-that-nobodys-talking-about-bitcode >=20 > Apparently Apple is either working on a McSema-esque technology or would = require the app to be (also?) provided in the form of LLVM-bitcode-IR (in a= ddition? to ARM-processor machine-code) at the time of submission to the Ap= p Store for approval. They're not doing anything of the sort. They used to use fat binaries conta= ining both m68k and powerpc, then both 32/64 bit x86. For this they'll use = LLVM bitcode, which is IR compiled to LLVM's bitcode, something that's been= in LLVM since it started. One of the major pros about that bitcode is that= you can then do aggressive linking and stripping before installation. We talked about a similar mechanism for a platform neutral binary for Amiga= OS NG BITD, but that never happened, well it did sort of with Tao, but it n= ever got anywhere and Tao went out of business.