From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gnu.wildebeest.org (wildebeest.demon.nl [212.238.236.112]) by sourceware.org (Postfix) with ESMTPS id 471A43850415 for ; Wed, 29 Jul 2020 11:53:40 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 471A43850415 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=klomp.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=mark@klomp.org Received: from tarox.wildebeest.org (tarox.wildebeest.org [172.31.17.39]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id F2310319BB30; Wed, 29 Jul 2020 13:53:38 +0200 (CEST) Received: by tarox.wildebeest.org (Postfix, from userid 1000) id A12CC4001E1F; Wed, 29 Jul 2020 13:53:38 +0200 (CEST) Message-ID: <616c0f661732fd1021e5a5b13ef872927390004d.camel@klomp.org> Subject: Re: ABI document From: Mark Wielaard To: Florian Weimer , gnu-gabi@sourceware.org Date: Wed, 29 Jul 2020 13:53:38 +0200 In-Reply-To: <87o8nypmpq.fsf@oldenburg2.str.redhat.com> References: <87o8nypmpq.fsf@oldenburg2.str.redhat.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Evolution 3.28.5 (3.28.5-8.el7) Mime-Version: 1.0 X-Spam-Status: No, score=-6.5 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: gnu-gabi@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gnu-gabi mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jul 2020 11:53:41 -0000 On Wed, 2020-07-29 at 13:47 +0200, Florian Weimer via Gnu-gabi wrote: > Is there an ABI document somewhere for the generic GNU ABI? >=20 > It would eventually collect things like symbol versioning, TLS, and some > of the smaller stuff. I understand those have been documented > separately so far, but the question is what we should do for new > features? There isn't a formal one specific to the generic GNU ABI. But we can set up a gnu-gabi git repo on sourceware for it, so we can collect those things. Or do you prefer a wiki? Cheers, Mark