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++/99576] [coroutines] destructor of a temporary called too early within co_await expression Date: Sun, 27 Nov 2022 15:42:51 +0000 [thread overview] Message-ID: <bug-99576-4-oDuENfXv6t@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99576-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99576 --- Comment #10 from Iain Sandoe <iains at gcc dot gnu.org> --- (In reply to Adrian Perl from comment #9) > Thanks for the advice. > > I hope you meant __builtin_trap() as I can't find a __builtin_abort() > function. hmm .. I meant __builtin_abort () ... it is widely used in the testsuite for the reasons mentioned (try grepping for it in gcc/testsuite/gcc.dg to see some examples). > I have now written test applications for all relevant bug reports (99576, > 100611, 101976, 101367). great! > I also verified that it fixes 107288, but did not add a test as it requires boost asio. The way to deal with cases like that is to take the .ii file (so that the dependencies on external headers are removed) and then reduce it to something usable as a test. Such reductions vary in difficulty (using tools like c-vise or creduce can help, sometimes it's possible to do it manually too). [I'm not asking you to do this right now, but mentioning that this is the approach used in such cases]. > Unfortunately I was wrong that the patch will fix 102217 and 101244. They > use similar examples but also the ternary operator, which still leads to an > invalid statement error when used in co_awaits. Yes, this is a different problem for which I have some work in progress, but not ready for publication just yet. > I will send the patch together with the testfiles as soon as the testsuite > has finished. Is it normal that it takes more than 6 hours to complete? depends on your hardware .. my fastest box takes about 2 hours, my slowest nearly a week :) .. so long as you are using "-jN" on the make line where N ≈ the number of threads your hardware will accommodate, that's about the best you can do. If you plan on working more with GCC there is also the option to get an account on the "compile farm" which gives you access to more platform versions and some quite powerful hardware.
next prev parent reply other threads:[~2022-11-27 15:42 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-13 13:54 [Bug c++/99576] New: [coroutines] desctructor " lemourin at gmail dot com 2021-05-14 16:21 ` [Bug c++/99576] [coroutines] destructor " nilsgladitz at gmail dot com 2021-05-15 12:31 ` nilsgladitz at gmail dot com 2021-06-10 14:14 ` davidledger at live dot com.au 2021-06-23 8:54 ` victor.burckel at gmail dot com 2021-10-01 19:57 ` iains at gcc dot gnu.org 2022-11-25 11:50 ` adrian.perl at web dot de 2022-11-25 15:13 ` iains at gcc dot gnu.org 2022-11-26 16:28 ` adrian.perl at web dot de 2022-11-26 16:40 ` iains at gcc dot gnu.org 2022-11-27 14:24 ` adrian.perl at web dot de 2022-11-27 15:42 ` iains at gcc dot gnu.org [this message] 2022-11-27 16:08 ` adrian.perl at web dot de 2022-11-28 19:13 ` adrian.perl at web dot de 2022-11-30 11:47 ` iains at gcc dot gnu.org 2022-11-30 23:38 ` iains at gcc dot gnu.org 2022-12-02 20:54 ` iains at gcc dot gnu.org 2022-12-04 10:41 ` cvs-commit at gcc dot gnu.org 2023-07-07 9:32 ` rguenth 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-99576-4-oDuENfXv6t@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).