From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id E7FFF3858414; Thu, 22 Feb 2024 09:45:27 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E7FFF3858414
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1708595127;
	bh=2ZGHc2yEpIt2FdhHGaRcgfYWN5L3f5xai4m1HncNpBA=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=YFZJVPpmC2+fnp+ZP+9EpyZ6WtFrP/vhJUoVFoav4TvnVxwvJeTuIW7E3kvSJZqVa
	 ZaSNi7dQzbBxIpqQwg1dIcQCHTKLAY3r2BLqKeZ0ks8pozrQvwEHB+PD4W5K5CEyip
	 UxuYmM9z3xFvUiwUZhoSa/Gh9MguEWZwsEpuDhyY=
From: "fxcoudert at gmail dot com" <gcc-bugzilla@gcc.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 09:45:27 +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: fxcoudert at gmail dot com
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: <bug-114007-4-sTcYL6NwjF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-114007-4@http.gcc.gnu.org/bugzilla/>
References: <bug-114007-4@http.gcc.gnu.org/bugzilla/>
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: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D114007

--- Comment #19 from fxcoudert at gmail dot com <fxcoudert at gmail dot com=
> ---
Hi Rainer,

> Thanks a lot for the patch.  I've now re-bootstrapped trunk on macOS 14
> with it applied instead of the local (incomplete) <sys/cdefs.h>
> workaround.

I haven=E2=80=99t yet tested Xcode 13.3 myself, and have only followed the =
PRs from far
away. Are there any issues (SDK, linker, or otherwise) that we need to repo=
rt
to Apple? Or that are already reported but we want taken more seriously?

I can use my channel through Homebrew to get them to prioritise it to some
extent. It=E2=80=99s probably too late for 13.3 at this point, but we shoul=
d get it
fixed anyway for later.

FX

--- Comment #20 from fxcoudert at gmail dot com <fxcoudert at gmail dot com=
> ---
Hi Rainer,

> Thanks a lot for the patch.  I've now re-bootstrapped trunk on macOS 14
> with it applied instead of the local (incomplete) <sys/cdefs.h>
> workaround.

I haven=E2=80=99t yet tested Xcode 13.3 myself, and have only followed the =
PRs from far
away. Are there any issues (SDK, linker, or otherwise) that we need to repo=
rt
to Apple? Or that are already reported but we want taken more seriously?

I can use my channel through Homebrew to get them to prioritise it to some
extent. It=E2=80=99s probably too late for 13.3 at this point, but we shoul=
d get it
fixed anyway for later.

FX=