From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 95EF43858D34; Thu, 22 Feb 2024 10:22:15 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 95EF43858D34 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1708597335; bh=5/biZF/+KJUr9K3clXFVALsLL/FaLB33h7X37WDbdvI=; h=From:To:Subject:Date:In-Reply-To:References:From; b=mZ0cXsP0g1X+5WDvtO7Rup51Bw64lg1q5YmVmDA7w4rxF6vQT5oTBhDB4iFSPDfjS /6LUprJ26I1rw4Tz23vgVouf6GChoQMpsv/vWn4Jpa4+BeTtUiF+bbwNevpPxnGEd8 obTFMgdCul8fDLfZ5PaDPn2iDPniRBoCVbcvD9gE= From: "jakub at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/114007] gcc chokes on __has_cpp_attribute(clang::unsafe_buffer_usage) Date: Thu, 22 Feb 2024 10:22:14 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: preprocessor X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org X-Bugzilla-Target-Milestone: 14.0 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=3D114007 --- Comment #24 from Jakub Jelinek --- (In reply to fxcoudert@gmail.com from comment #19) > I haven=E2=80=99t yet tested Xcode 13.3 myself, and have only followed th= e PRs from > far away. Are there any issues (SDK, linker, or otherwise) that we need to > report to Apple? Or that are already reported but we want taken more > seriously? Do they use [[clang::unsafe_buffer_usage]] then if __has_safe_buffers is defined even in -std=3Dc11 etc. modes in the headers? Even clang errors on [[clang::unsafe_buffer_usage]] with -std=3Dc11 -pedantic-errors... Though, guess not an issue for GCC itself, because if the parsing of __has_cpp_attribute is fixed, then GCC definitely will not yield 1 for clang::unsafe_buffer_usage attribute...=