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 autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 2002:a24:47c7:: with SMTP id t190-v6mr3497027itb.35.1526654037975; Fri, 18 May 2018 07:33:57 -0700 (PDT) X-Received: by 2002:a9d:70d1:: with SMTP id w17-v6mr163729otj.5.1526654037416; Fri, 18 May 2018 07:33:57 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!news.gegeweb.eu!gegeweb.org!news.redatomik.org!newsfeed.xs4all.nl!newsfeed9.news.xs4all.nl!85.12.16.68.MISMATCH!peer01.ams1!peer.ams1.xlned.com!news.xlned.com!peer01.am4!peer.am4.highwinds-media.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!v8-v6no1652735itc.0!news-out.google.com!f20-v6ni1871itd.0!nntp.google.com!v8-v6no1652729itc.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Fri, 18 May 2018 07:33:57 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=47.185.233.194; posting-account=zwxLlwoAAAChLBU7oraRzNDnqQYkYbpo NNTP-Posting-Host: 47.185.233.194 References: <9169bb0d-626f-4f6d-82c9-8a9b7543a084@googlegroups.com> <92b78739-e2c5-4e45-bbd8-f80ec4918691@googlegroups.com> <6dc39990-16eb-4717-8b8a-1d41c2767530@googlegroups.com> <1103700103.548265160.819002.laguest-archeia.com@nntp.aioe.org> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <5c0d9fbd-0dfc-4d6d-98b3-cbcceda3b67c@googlegroups.com> Subject: Re: disruptors of & inventory of Ada compilers and latest their era of ISO8652 compliance From: "Dan'l Miller" Injection-Date: Fri, 18 May 2018 14:33:57 +0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Received-Bytes: 4201 X-Received-Body-CRC: 1408680917 Xref: reader02.eternal-september.org comp.lang.ada:52433 Date: 2018-05-18T07:33:57-07:00 List-Id: On Friday, May 18, 2018 at 9:06:19 AM UTC-5, R R wrote: > On Thursday, May 17, 2018 at 8:42:55 PM UTC+2, Niklas Holsti wrote: > > On 18-05-17 18:56 , Luke A. Guest wrote: > > > > > > See previous discussions about taking gcc=E2=80=99s ir and the ramifi= cations of > > > doing so, it makes the resultant code gplv3. It=E2=80=99s in the gcc = faq and > > > licence. > >=20 > > Firefox cannot find the word "intermediate" or the (upper-case) acronym= =20 > > "IR" in the GPL FAQ at https://www.gnu.org/licenses/gpl-faq.html. The= =20 > > word "representation" occurs once, in a different context. > >=20 > > Ditto for the GPLv3 itself, at https://www.gnu.org/licenses/gpl.txt. > >=20 > > If you extract a source-to-IR "front compiler" from the full gcc, of=20 > > course that front-compiler itself remains under GPL. But I do not=20 > > believe that IR text generated by that compiler would automatically fal= l=20 > > under the GPL, no more than machine code generated by the full gcc=20 > > automatically falls under the GPL. > >=20 > > Please provide a link or quotation to support your claim. >=20 > I remember discussions (from the 90ies ?) that it would be possible to ge= nerate source code from the IR. If that generated source code had not any c= opyright (ie GPL), you would have a GPL-strip compiler GPL C/Ada-code to C/= Ada-code without any copyright.=20 >=20 > R But GPLv3's =E2=80=9CTarget Code=E2=80=9D clauses were devised to overtly p= rohibit utilizing such techniques; the resulting IR and downstream derivati= ve works are all GPLv3 (regardless of the original source code's license) i= f a GPLv3ed toolchain was utilized to produce the IR. Btw, under nearly all licenses other than GPLv3, LGPLv3, and AGPLv3, this p= articular technique would still result in a derivative work of the original= source code under U.S. copyright law, which would mean that the generated-= from-IR source code would still have the exact same rights-to-copy license = as the original source code (e.g., GPLv2, MIT, Apache, public domain), unle= ss the IR was produced by a GPLv3 toolchain in which the original source co= de's license is overridden by GPLv3 instead. (GPLv3 increased the strength= of the viral spread via the =E2=80=9CTarget Code=E2=80=9D clauses. Likewi= se with the Runtime Exception for GPLv3, because the Runtime Exception revo= kes itself in certain situations, one of which is IR.)