public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/100897] Symmetric transfer does not prevent stack-overflow for C++20 coroutines Date: Fri, 11 Jun 2021 07:36:57 +0000 [thread overview] Message-ID: <bug-100897-4-DmLz0UrdQ5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100897-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100897 Iain Sandoe <iains at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Last reconfirmed| |2021-06-11 See Also| |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=94794, | |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=95137 --- Comment #1 from Iain Sandoe <iains at gcc dot gnu.org> --- for symmetric transfer to work without stack overflow, it relies on an indirect tailcall. For some GCC targets indirect tail-calls are not available without some additional support (see PR94794). I tried to reproduce this (with a test case I use regularly for this) on a target that normally completes symmetric transfers successfully when the optimisation level is > 1. (x86_64, darwin). The fail also occurs with my regular test case with -fsanitize=address - so, it seems that the inclusion of the address sanitiser is preventing or interfering with the tailcall. Note that there are also other known issues with coroutines and the sanitizers (PR95137).
next prev parent reply other threads:[~2021-06-11 7:36 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-03 20:03 [Bug c++/100897] New: " l.v.merzljak at gmail dot com 2021-06-11 7:36 ` iains at gcc dot gnu.org [this message] 2021-06-11 10:33 ` [Bug c++/100897] " l.v.merzljak at gmail dot com 2021-06-11 11:17 ` iains at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-100897-4-DmLz0UrdQ5@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).