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 EC2D53858CDB; Thu, 13 Jul 2023 15:41:03 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org EC2D53858CDB
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1689262863;
	bh=fo+4i0ZJ/Hwqbmt1XsliezWkHqCfwGtcdo0b+TPS6aw=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=SPsEDW/WAeFZ9gdIgbUROQ3tR1lC7Hm3Sy8WLKvSR86SplDzUZYiwX5XWbYiKT1D0
	 JlkE03j4E0oYvzOwINxX5CcpA4iXV2wCj+0ifv3uDQVt/y1u20g6qqGMxzrVvb1jq1
	 jhT9IOHFjkQhfAWQyj8fBvMskS83z9CzFQRMo5sE=
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/110654] inconsistent error message in presence of unexpected
 encoded characters
Date: Thu, 13 Jul 2023 15:41:02 +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: 13.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: <bug-110654-4-9mVJyE8w0M@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-110654-4@http.gcc.gnu.org/bugzilla/>
References: <bug-110654-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=3D110654

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
libccp has:
          /* In C++, this is an error for invalid character in an identifier
             because logically, the UTF-8 was converted to a UCN during
             translation phase 1 (even though we don't physically do it that
             way).  In C, this byte rather becomes grammatically a separate
             token.  */

          if (CPP_OPTION (pfile, cplusplus))
            cpp_error (pfile, CPP_DL_ERROR,
                       "extended character %.*s is not valid in an identifi=
er",
                       (int) (*pstr - base), base);
          else
            {
              *pstr =3D base;
              return false;
            }


So this is due to differences in the languages themselves rather than due t=
o C
vs C++ front-end ...=