From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) by sourceware.org (Postfix) with ESMTP id 5277038708F3 for ; Wed, 4 Nov 2020 09:40:49 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 5277038708F3 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-517-D9Pm_LWINnK1ISFbySv6sQ-1; Wed, 04 Nov 2020 04:40:47 -0500 X-MC-Unique: D9Pm_LWINnK1ISFbySv6sQ-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 401F664159; Wed, 4 Nov 2020 09:40:46 +0000 (UTC) Received: from oldenburg2.str.redhat.com (ovpn-113-12.ams2.redhat.com [10.36.113.12]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 6FEDC7E160; Wed, 4 Nov 2020 09:40:39 +0000 (UTC) From: Florian Weimer To: Jakub Jelinek Cc: Siddhesh Poyarekar , libc-alpha@sourceware.org, sguelton@redhat.com Subject: Re: [PATCH] Remove __warn_memset_zero_len [bz #25399] References: <20201104090547.1376086-1-siddhesh@sourceware.org> <87o8kd4gyq.fsf@oldenburg2.str.redhat.com> <20201104093619.GR3788@tucnak> Date: Wed, 04 Nov 2020 10:40:37 +0100 In-Reply-To: <20201104093619.GR3788@tucnak> (Jakub Jelinek's message of "Wed, 4 Nov 2020 10:36:19 +0100") Message-ID: <87d00t4fze.fsf@oldenburg2.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-Spam-Status: No, score=-6.2 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_H4, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: libc-alpha@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-alpha mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Nov 2020 09:40:50 -0000 * Jakub Jelinek: > It is ok if it doesn't warn anymore, and it is ok if it is not in the > headers anymore, but one can still have object files or *.a libraries > compiled with gcc 4.9 and earlier against older glibc and that will > now fail to link altogether. In general, that is not supported. We have recently made an exception for __xstat. But in this case, linking after removal will only fail if there was an annoying linker warning before, so I think it's going to be very rare that this makes a difference. Thanks, Florian -- Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill