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 3547B3858033; Fri,  2 Feb 2024 15:48:21 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3547B3858033
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1706888901;
	bh=6cCYBrO41MdzNr9+uc0uYNfyBDQPOydeaBxloVKXq7o=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=qhfg64bpapdoYRivJHn/VL2NFTxSrg/STAbOF3QVRKuAUZdXN1F7b/Mz0EGUQ1x31
	 lORjsxbwhDkWTQuedpPb9gxmmzKRC+oo1EKu1kwL2r6kz40E7QbHGZto9KzCtLB6ma
	 i3ad6m0bTu15muReygvjMoWJmuDj8MS5pKva21+o=
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/104739] gdc.test/runnable/mangle.d etc. FAIL with Solaris as
Date: Fri, 02 Feb 2024 15:48:20 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: d
X-Bugzilla-Version: 12.0
X-Bugzilla-Keywords: assemble-failure, testsuite-fail
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ro at CeBiTec dot Uni-Bielefeld.DE
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ibuclaw at gdcproject dot org
X-Bugzilla-Target-Milestone: 12.4
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-104739-4-ZhNfevN6tO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-104739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-104739-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=3D104739

--- Comment #5 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot U=
ni-Bielefeld.DE> ---
> --- Comment #4 from Rainer Orth <ro at gcc dot gnu.org> ---
> I wonder how to handle this: while DejaGnu has an ucn effective-target ke=
yword,
> the gdc.test testsuite doesn't use those at all.

What I think could be done is

* Add "//UTF-8 chars" comments to testmodule.d and ufcs.d; mangle.d
  already has one.

* Make gdc-utils.exp (gdc-convert-test) check for those annotations,
  adding

  // { dg-require-effective-target ucn}

  if found.

The new annotations would have to go upstream, I believe.  WDYT?=