From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on ip-172-31-74-118.ec2.internal X-Spam-Level: X-Spam-Status: No, score=-2.9 required=3.0 tests=BAYES_00,NICE_REPLY_A autolearn=ham autolearn_force=no version=3.4.6 Path: eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail From: "J-P. Rosen" Newsgroups: comp.lang.ada Subject: Re: How to challenge a GCC patch? Date: Mon, 27 Sep 2021 16:20:05 +0200 Organization: Adalog Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Mon, 27 Sep 2021 14:20:02 -0000 (UTC) Injection-Info: reader02.eternal-september.org; posting-host="6df88795bae05d9d6ac6ff15369bb4fc"; logging-data="30266"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19VOmfQ4uoZRYAZlOaYG2ob" User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 Cancel-Lock: sha1:i3k12dZkk1zjoRcphZ8j/6CWXqw= In-Reply-To: Content-Language: fr Xref: reader02.eternal-september.org comp.lang.ada:62844 List-Id: Le 27/09/2021 à 14:48, Simon Wright a écrit : > "J-P. Rosen" writes: > >> AdaCore has introduced a patch in FSF GCC to remove ASIS support. >> >> AdaCore is free to do what they want with their own version of >> GCC. However, removing a useful feature from the FSF version with the >> goal to promote their own, in-house tool is clearly against the spirit >> of free software. >> >> Does anybody know the procedures set by the FSF to challenge a patch? > > It's not just the patch(es), it's any subsequent changes to affected > parts of the compiler. > Right, if they want to contribute further patches, they'll have to keep it ASIS compatible. That's not a reason to divert gcc to support their own private interest. -- J-P. Rosen Adalog 2 rue du Docteur Lombard, 92441 Issy-les-Moulineaux CEDEX Tel: +33 1 45 29 21 52 https://www.adalog.fr