public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rafael at espindo dot la" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/95137] Sanitizers seem to be missing support for coroutines
Date: Mon, 22 Jun 2020 16:19:20 +0000 [thread overview]
Message-ID: <bug-95137-4-aUjlx0HsgW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95137-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95137
Rafael Avila de Espindola <rafael at espindo dot la> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #48723|0 |1
is obsolete| |
--- Comment #29 from Rafael Avila de Espindola <rafael at espindo dot la> ---
Created attachment 48771
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48771&action=edit
Testcase without lambda coroutines
I modified the testcase to also build with clang and not depend on async
lambdas. This still reproduces the problem with gcc with undefined behaviour
sanitizer, but works with with clang and sanitizers and gcc with valgrind.
next prev parent reply other threads:[~2020-06-22 16:19 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 18:00 [Bug sanitizer/95137] New: " rafael at espindo dot la
2020-05-14 18:16 ` [Bug sanitizer/95137] " jakub at gcc dot gnu.org
2020-05-14 18:53 ` iains at gcc dot gnu.org
2020-05-15 9:26 ` marxin at gcc dot gnu.org
2020-05-15 22:42 ` rafael at espindo dot la
2020-05-15 22:43 ` rafael at espindo dot la
2020-05-18 6:11 ` marxin at gcc dot gnu.org
2020-05-18 7:24 ` marxin at gcc dot gnu.org
2020-05-18 7:24 ` marxin at gcc dot gnu.org
2020-05-18 8:16 ` iains at gcc dot gnu.org
2020-05-19 10:47 ` iains at gcc dot gnu.org
2020-05-19 10:51 ` iains at gcc dot gnu.org
2020-05-19 20:37 ` rafael at espindo dot la
2020-05-20 10:48 ` iains at gcc dot gnu.org
2020-05-20 11:06 ` marxin at gcc dot gnu.org
2020-05-20 11:19 ` iains at gcc dot gnu.org
2020-05-20 20:04 ` rafael at espindo dot la
2020-05-20 20:08 ` avi@cloudius-systems.com
2020-05-20 20:15 ` rafael at espindo dot la
2020-05-22 1:05 ` rafael at espindo dot la
2020-05-22 1:07 ` rafael at espindo dot la
2020-05-22 11:23 ` iains at gcc dot gnu.org
2020-05-27 19:43 ` iains at gcc dot gnu.org
2020-05-31 12:42 ` avi@cloudius-systems.com
2020-05-31 13:22 ` iains at gcc dot gnu.org
2020-06-09 19:52 ` cvs-commit at gcc dot gnu.org
2020-06-10 15:11 ` rafael at espindo dot la
2020-06-10 15:21 ` iains at gcc dot gnu.org
2020-06-11 18:57 ` cvs-commit at gcc dot gnu.org
2020-06-12 18:37 ` rafael at espindo dot la
2020-06-22 16:19 ` rafael at espindo dot la [this message]
2020-06-22 16:53 ` iains at gcc dot gnu.org
2020-07-21 19:39 ` rafael at espindo dot la
2020-07-21 20:39 ` iains at gcc dot gnu.org
2020-07-23 6:51 ` rguenth at gcc dot gnu.org
2020-08-12 9:39 ` niekb at scintilla dot utwente.nl
2020-08-17 8:52 ` iains at gcc dot gnu.org
2020-11-11 20:11 ` avi@cloudius-systems.com
2020-11-12 13:21 ` iains at gcc dot gnu.org
2020-11-12 13:54 ` avi@cloudius-systems.com
2021-02-09 9:41 ` niekb at scintilla dot utwente.nl
2021-02-09 9:43 ` iains at gcc dot gnu.org
2021-04-08 12:02 ` rguenth at gcc dot gnu.org
2021-05-04 12:32 ` rguenth at gcc dot gnu.org
2021-05-21 10:21 ` stream009 at gmail dot com
2021-09-28 19:56 ` niekb at scintilla dot utwente.nl
2021-09-28 20:05 ` iains at gcc dot gnu.org
2021-09-28 20:56 ` rafael at espindo dot la
2022-01-30 23:37 ` pobrn at protonmail dot com
2022-02-15 16:50 ` jakub at gcc dot gnu.org
2022-02-15 17:56 ` iains at gcc dot gnu.org
2022-03-24 12:29 ` valera.mironow at gmail dot com
2022-03-24 12:45 ` avi at scylladb dot com
2022-03-24 12:52 ` valera.mironow at gmail dot com
2022-03-24 12:56 ` marxin at gcc dot gnu.org
2022-03-24 12:56 ` marxin at gcc dot gnu.org
2022-03-24 13:02 ` 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-95137-4-aUjlx0HsgW@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: link
Be 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).