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: Sat, 26 Nov 2022 16:40:49 +0000 [thread overview] Message-ID: <bug-99576-4-S9IyIlyXEC@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 #8 from Iain Sandoe <iains at gcc dot gnu.org> --- (In reply to Adrian Perl from comment #7) Again, thanks for working on this. > Bootstrapping was successfull and the tests are currently running. Some of > the tests have failed, but they don't seem to be related to coroutines. On most platforms, at any given point in the cycle, there will be failing tests... > Should I test twice, with and without the patch, in order to see the actual > impact? ... so ,yes, that is the usual approac. there are some tools that help you compare the results. I personally use: ${src}/contrib/test_summary > summ.txt and then the same in the patched build tree ... ... and then compare the two summ.txt files side-by side using diff -> less. (it is important that the same number of tests are executed of course, so the numbers are relevant as well as the pass/fail). Your number for g++ should be bigger by the ones added. > Most of the test-applications attached and posted in the bug reports only > log to stdout/stderr. Should I rewrite them and add assertions? The usual mechanism is to do a test and to abort()*** on fail [an assert is equivalent]. The reason for the abort() rather than, say, returning non-zero from main is that when tests are conducted on remote embedded platforms, the return value from main() might not be available. *** For c++ tests, the extra of pulling in <cassert> or <cstdlib> is likely not significant, but if you want to avoid that (it can make debugging easier to reduce the number of headers pulled in) .. then you can use __builtin_abort();
next prev parent reply other threads:[~2022-11-26 16:40 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 [this message] 2022-11-27 14:24 ` adrian.perl at web dot de 2022-11-27 15:42 ` iains at gcc dot gnu.org 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-S9IyIlyXEC@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).