From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 5836C3858D3C; Tue, 29 Nov 2022 18:59:27 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5836C3858D3C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1669748367; bh=tGvb/mhxuTqUM04aOtD3hnqrPoNHQh10dIArCGwOjFk=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Ig46T3/6B0ut95Dc1PDFlQ7TWkGlRYO9evr5Hc4tuSWFDuz7/MaviXHvR8DTcnQ0W OlcABoC9RnH6CeZHKOVHeR/LlwmNiEtVExm2UEsfkqkIUWjdkWEhke+e2De3EcbPnZ YDWQYcmCoh6S7/I9NK9tkhJFuq2iMSYOBMljN7n0= From: "joseph at codesourcery dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug other/55899] GCC should provide built-ins in data types flavor/version/variation Date: Tue, 29 Nov 2022 18:59:26 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: other X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: joseph at codesourcery dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: 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: 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=3D55899 --- Comment #3 from joseph at codesourcery dot com --- C2x provides type-generic versions of various such operations,=20 in addition to type-specific versions (but the type-specific versions are=20 for unsigned char through unsigned long long, so don't themselves address=20 the issue from this PR, and my view is that type-generic functions are=20 error-prone in cases, such as clz, where the result depends on the type=20 and not just the integer value of the argument). Since is a library facility (with functions thus expected to be= =20 available with external linkage to link against whether or not the header=20 is included) I expect to implement it in due course in glibc, not GCC,=20 though as usual built-in functions with the standard names would be=20 appropriate in GCC.=