From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 92F533858C2D; Sun, 3 Dec 2023 04:17:14 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 92F533858C2D DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1701577034; bh=UB4PJ37aVuiywVZlzmmhh90rx/3v1suOcfZEJiVxoLg=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Pa8n0stMFYiss8whMbCkRuOeexIIIyfLFxg2N20Q96kjeHVX24GLtC9FWynZRKoGf WprPjiS72WQ+NaTsjTrtpIPeg50PUuM1SiTDrO6/sL6wy1BhnO65q/H+CUQdW+b/+k i6m/PJdV7nNKkOi30wqXi7Zr/TJgDXlZ2ANH+K4Y= From: "xry111 at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/112789] Missing clang __builtin_ctzs for short Date: Sun, 03 Dec 2023 04:17:11 +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: 14.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: xry111 at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: WONTFIX X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D112789 Xi Ruoyao changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xry111 at gcc dot gnu.org --- Comment #13 from Xi Ruoyao --- (In reply to gnzlbg from comment #8) > Oh! Sorry! I see this was resolved as WONTFIX. >=20 > Does that mean that GCC, in contrast with the LLVM community - which is > always super helpful and friendly when it comes to trying to enable their > toolchains to compile SW developed with GNU - intentionally does not want= to > enable the GNU toolchains to compile SW developed with clang?=20 Because Clang developers actively claim to support GNU extensions, while GCC never has such a policy to support other extensions. When an extension is considered useful we port it, but in this case we already have __builtin_ct= zg as all others have mentioned. And Clang developers also reject GNU extensions if they consider the extens= ion "wrong", despite they make such a "compatibility" claim. In the future (when C23 is widely adopted) people should just use stdc_trailing_zerosus instead of directly invoking __builtin_ctz{g,s} of whatever compiler.=