From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from xry111.site (xry111.site [IPv6:2001:470:683e::1]) by sourceware.org (Postfix) with ESMTPS id 7077E3857705 for ; Tue, 11 Jul 2023 13:22:47 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 7077E3857705 Authentication-Results: sourceware.org; dmarc=pass (p=reject dis=none) header.from=xry111.site Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=xry111.site DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=xry111.site; s=default; t=1689081764; bh=DTiSB+ErGLcZm2Xix/6PGb+nb+ZxKNbgAC5nEQzUqO4=; h=Subject:From:To:Cc:Date:In-Reply-To:References:From; b=A92OIcSBFYcM4tUZ2myvtzhIumZGcx0aNrhhrloZKLEnawszxOP1rSlKOZUltn2Vd 7h+mEEDApB85MMbTkuu4aB1pavqBGjkQwDUZMqfG2uc17li7EsjVGePFHMqYWstcFN Rz1NVDmAmTQNU/iYEk077K0/FoAiEbQYnndKtP9Y= Received: from [192.168.124.11] (unknown [113.140.11.5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature ECDSA (P-384) server-digest SHA384) (Client did not present a certificate) (Authenticated sender: xry111@xry111.site) by xry111.site (Postfix) with ESMTPSA id 81DDB6644D; Tue, 11 Jul 2023 09:22:43 -0400 (EDT) Message-ID: <0867b39d59162428d9092d1ffbc02ec4c0008b47.camel@xry111.site> Subject: Re: [RFC v1 0/2] Use -fno-delete-null-pointer-checks to build glibc From: Xi Ruoyao To: Alejandro Colomar , libc-alpha@sourceware.org Cc: Florian Weimer , Sam James , Richard Biener , Andrew Pinski Date: Tue, 11 Jul 2023 21:22:41 +0800 In-Reply-To: <20230711131105.19203-1-alx@kernel.org> References: <20230711131105.19203-1-alx@kernel.org> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.48.4 MIME-Version: 1.0 X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,LIKELY_SPAM_FROM,SPF_HELO_PASS,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On Tue, 2023-07-11 at 15:11 +0200, Alejandro Colomar wrote: > Florian reported that there's -fno-delete-null-pointer-checks to tell > the compiler to not optimize, and only warn about incorrect uses of null > pointers. One potential problem is -fno-delete-null-pointer-checks not only disables optimizations based on __nonnull, but also disables the optimizations based on other provable non-null pointer values. So maybe we should run a benchmark to see if there is some severe degradation, if there is any we may fix it by moving null checks away from hot paths.=20 --=20 Xi Ruoyao School of Aerospace Science and Technology, Xidian University