From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id DA260388A008; Thu, 2 Apr 2020 11:26:55 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org DA260388A008 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1585826815; bh=lSMHw+Fso6rulDsIo9ZTR6I19R6l/KizwY20/jYiE0o=; h=From:To:Subject:Date:In-Reply-To:References:From; b=uL1AxetoYth3cS/hLu578EcvcCseRsFBCMxhBWxZ1Ieog/ZxQpJI4hAhuQgspmrxm ybnXfa7Wny+M/owYr8LnzLPqYQZhPDFb9Cr7Ov2k925CMcifQ3UMRlvzfgr1gvlULi NBH3TLw6lO4WExCsA+xB8oK0GBCzC4K9/W8B3s34= From: "iains at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/94359] new test case g++.dg/coroutines/torture/symmetric-transfer-00-basic.C fails Date: Thu, 02 Apr 2020 11:26:55 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 10.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: iains at gcc dot gnu.org X-Bugzilla-Status: NEW 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: 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 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Apr 2020 11:26:56 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D94359 --- Comment #8 from Iain Sandoe --- (In reply to Rainer Orth from comment #7) > I'm seeing the same failure on Solaris/SPARC (32 and 64-bit). Do you have any info on why the tail-call fails there? (e.g. is it not possible to make an indirect tail-call in the ABI, as seems= to be the case for powerpc64 & AIX). At present, having discussed with a couple of other folks, my plan (for sta= ge 4) is to produce a target hook to allow targets to opt out. For next stage 1, since the caller and the callee are both under our control and it is known that the callee *must* be another coroutine 'actor' functio= n it might be possible to work around specific target constraints.=