From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id A55F8385E00B; Sat, 28 Mar 2020 16:10:38 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A55F8385E00B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1585411838; bh=URRGqZeY3WbKKqUZ4IwwZRP2flVrmMBtc0DCaipjyOQ=; h=From:To:Subject:Date:In-Reply-To:References:From; b=DxwO4ABViuYgHOra+mw09pBKAGQ/AfavZvn5+TlXWjQHN2mXGCMbzdaBZHvOteK8C D6db/KgdigM0FpCjtL1IO7Ft/mBtFG0uWyewc1dqaMmm9ajx+zuEExXeW8bygG5ftE SIKgDOeuqYGLiC09WL/bF6kT5ME/gjc61K5K2zP4= 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: Sat, 28 Mar 2020 16:10:38 +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: Sat, 28 Mar 2020 16:10:38 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D94359 --- Comment #5 from Iain Sandoe --- (In reply to Iain Sandoe from comment #4) > So not sure how to proceed here at the moment (I wonder if this works for > PPC on the clang impl). It does work for X86 (and ironically, on PPC Darwin too - where the fact th= at we build a new "got" in each routine + no use of TOC means we can always ta= il call). Actually, I'm a bit suspicious of what happens in the case that two coroutines are in different DSOs for X86. apparently not: [iains@gcc1-power7 llvm-90]$ ./INSTL/bin/clang++ -fcoroutines-ts -std=3Dc++= 17 ../gcc-master/src/gcc/testsuite/g++.dg/coroutines/torture/symmetric-transfe= r-00-basic.C -stdlib=3Dlibc++ -S fatal error: error in backend: failed to perform tail call elimination on a call site marked musttail (the test case crashes the compiler for O>0). [iains@gcc1-power7 llvm-10]$ ./INSTL/bin/clang++ -fcoroutines-ts -std=3Dc++= 17 ../gcc-master/src/gcc/testsuite/g++.dg/coroutines/torture/symmetric-transfe= r-00-basic.C -stdlib=3Dlibc++ -S fatal error: error in backend: failed to perform tail call elimination on a call site marked musttail I'm going to discuss this with the coroutines paper authors - as to whether= any constraints had been considered. Note, once again, that failure to impleme= nt this does not make us non-conforming.=