From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 0232639D4E5C; Thu, 6 Jun 2024 07:50:14 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0232639D4E5C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1717660215; bh=EKdxWHESvrCGKl/jHW8aEeFaXpO0r3feD2NDG60fCPE=; h=From:To:Subject:Date:In-Reply-To:References:From; b=jUkkdz8jQtonkhD3i+rQnJLIHbmDCdPEUm4qO6lF2oMBEqlL0dBhIKU2T0aYYX83a guObHAb2rcwd+kwPaARggEJ1okauwDc4fsI1LFPaNwalD/M1aC1MN8ASl34HOvLXmH kC6SR0xrKvnGW0S8NiJ2nrbTIyLWwJOuyQeiIxPI= From: "aoliva at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/114803] simd conversion to [[gnu::vector_size(N)]] type hits invalid code in experimental/bits/simd_builtin.h Date: Thu, 06 Jun 2024 07:50:13 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: aoliva at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: mkretz 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=3D114803 --- Comment #16 from Alexandre Oliva --- That macro is used within libstdc++ to avoid relying on C99 functions when = the target C library is not C99-compliant. It involves leaving out C++ standard bits that would depend on functions that the C library doesn't offer, inclu= ding some of the declarations in ::std::. IMHO it would make sense to omit simd functions corresponding to C99/TR1 on= es known to be missing. Now, it's unclear to me whether we'd be better off omitting the entire set of C99/TR1 math functions as a block, or whether there'd be any benefit from considering individual functions separately.=20 newlib, for example, exports a number of the C99/TR1 functions, but not all= of them, so the macro is not defined.=