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 E2CB33858415; Fri,  1 Dec 2023 12:56:45 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E2CB33858415
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1701435405;
	bh=PK4rSR3O2vCMB6U0rpIlLvhdbVPj7wR/yKUyX48HpG4=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=HwDmFtUB9Ll2ouvNbww+Zx6QP3xaECndsYuQaQhUnEA0VZ0sORJr0cziC1kf1gneP
	 fO4Ax9vaf/hrz4m5lQXRXs+rVoVEeBH8Dx17jSyhOyFkCT/zqCU8lMb99gl6sPGI9Q
	 jLIsHFcO4eBBTmDCLZsF6DQibLFw/f3Kd5amYJz4=
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/112728] gcc.dg/scantest-lto.c FAILs
Date: Fri, 01 Dec 2023 12:56:44 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 14.0
X-Bugzilla-Keywords: testsuite-fail
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ro at CeBiTec dot Uni-Bielefeld.DE
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: 14.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-112728-4-1uR7iOPkDl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-112728-4@http.gcc.gnu.org/bugzilla/>
References: <bug-112728-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=3D112728

--- Comment #4 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot U=
ni-Bielefeld.DE> ---
> --- Comment #3 from Jorn Wolfgang Rennecke <amylaar at gcc dot gnu.org> -=
--
> (In reply to Rainer Orth from comment #0)
>> The gcc.dg/scantest-lto.c FAILs on quite a number of targets:
> ...=20
>> * On Darwin, the __TEXT,__eh_frame contains .ascii because the assembler
>>   lacks support for cfi directives.
>
> I suppose we could handle the darwin case by:
>
> - Not doing the common scan-assembler* tests for darwin

I guess it would be better to use the recently introduce cfi
effective-target keyword to catch targets that would show ascii in
there.

> - doing a scan-assembler-times test that expects exactly how many .ascii =
are
> emitted for cfi.

While that's an option, I suspect that's going too far actually.=