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=-1.9 required=3.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.6
Path: eternal-september.org!reader02.eternal-september.org!aioe.org!RKN7TKnHC01q0gdg6EhkbQ.user.46.165.242.75.POSTED!not-for-mail
From: Simon Wright <simon@pushface.org>
Newsgroups: comp.lang.ada
Subject: Re: How to challenge a GCC patch?
Date: Mon, 27 Sep 2021 13:48:30 +0100
Organization: Aioe.org NNTP Server
Message-ID: <lyr1dab2w1.fsf@pushface.org>
References: <sis53t$du1$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain
Injection-Info: gioia.aioe.org; logging-data="5456"; posting-host="RKN7TKnHC01q0gdg6EhkbQ.user.gioia.aioe.org"; mail-complaints-to="abuse@aioe.org";
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (darwin)
X-Notice: Filtered by postfilter v. 0.9.2
Cancel-Lock: sha1:7OE3Evi8JI9eEpobXp9CcQSYPvo=
Xref: reader02.eternal-september.org comp.lang.ada:62842
List-Id: <comp.lang.ada>

"J-P. Rosen" <rosen@adalog.fr> 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.