From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-1.mimecast.com (us-smtp-delivery-1.mimecast.com [205.139.110.120]) by sourceware.org (Postfix) with ESMTP id C78403850424 for ; Mon, 13 Jul 2020 10:47:14 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org C78403850424 Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-494-F0rng1zBOGexPEzUix9RAA-1; Mon, 13 Jul 2020 06:47:07 -0400 X-MC-Unique: F0rng1zBOGexPEzUix9RAA-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 8226519200C0; Mon, 13 Jul 2020 10:47:04 +0000 (UTC) Received: from oldenburg2.str.redhat.com (ovpn-112-235.ams2.redhat.com [10.36.112.235]) by smtp.corp.redhat.com (Postfix) with ESMTPS id CA0FE724C3; Mon, 13 Jul 2020 10:47:02 +0000 (UTC) From: Florian Weimer To: Matthias Klose Cc: Tom Tromey , Anthony Green , s.mesoraca16@gmail.com, "H.J. Lu" , landonf@freebsd.org, libffi-discuss , arigo@tunes.org Subject: Re: Another libffi ABI change and another release References: <871rqjmv05.fsf@tromey.com> <8736ayha1j.fsf@tromey.com> Date: Mon, 13 Jul 2020 12:47:01 +0200 In-Reply-To: (Matthias Klose's message of "Mon, 13 Jul 2020 11:58:23 +0200") Message-ID: <87lfjnsndm.fsf@oldenburg2.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-Spam-Status: No, score=2.1 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2, SPAM_URI, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: libffi-discuss@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libffi-discuss mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jul 2020 10:47:16 -0000 * Matthias Klose: > On 2/25/20 6:05 PM, Tom Tromey wrote: >> Anthony> Yes, some of them were related to trampoline layouts, which aren't relevant >> Anthony> if we go this route... >> Anthony> http://sourceware-org.1504.n7.nabble.com/Crashes-of-libffi-when-using-W-X-memory-and-forks-td412729.html >> Anthony> ...which is what I'd like to do. >> >> The ones I was thinking of were in this thread >> >> https://sourceware.org/ml/libffi-discuss/2015/msg00090.html >> >> But AFAIK there aren't patches for any of these ideas. > > I have now the request to enable CET in a distro, and before bumping > the soname myself, or invent an arbitrary soname which won't be used > by upstream, I'd like to ask if an upstream release could be cut now, > without repeating the multi-year release process we had with libffi > 3.3. Which soname do you use right now? Thanks, Florian