From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id F19B13896C16; Tue, 26 May 2020 23:13:08 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org F19B13896C16 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1590534788; bh=GwMigSJsa4TG6k4EgqRdFVtNCog383UmEvldf7kdhOg=; h=From:To:Subject:Date:In-Reply-To:References:From; b=EMfYJvAkQWScVdAZdSmpKeHjXHJpRvnTzXMM+dH9QXJKFh8qq8n5ZOfngbrThhpb+ tq6T43k7ZFkAx9X5LjMtwtoBDvnDS0ZvsxpUbm1N1wlL+eGKpXcSF7aOPScPzkrIS2 Wu7jCXr14mLg1fEolLuIpdruYEHRHiByZVGhzDXQ= From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/95242] [10/11 Regression] spurious "warning: zero as null pointer constant [-Wzero-as-null-pointer-constant]" on comparisons with -std=c++2a Date: Tue, 26 May 2020 23:13:08 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 10.1.0 X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: jason at gcc dot gnu.org X-Bugzilla-Target-Milestone: 10.2 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 May 2020 23:13:09 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D95242 --- Comment #2 from Jonathan Wakely --- Another way to implement the __unspec constructor would be: consteval __unspec(int __n) { if (__n !=3D 0) throw __n; } But I think I discussed this with Richard Smith in Prague and we realised t= here was a problem with it, but I might be misremembering.=