public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/94910] detect_stack_use_after_return=1 is much slower than clang's Date: Mon, 04 May 2020 05:27:39 +0000 [thread overview] Message-ID: <bug-94910-4-L02F6Mypi1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94910-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94910 Martin Liška <marxin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2020-05-04 Assignee|unassigned at gcc dot gnu.org |marxin at gcc dot gnu.org --- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> --- Thanks for the report, I'll take a look.
next prev parent reply other threads:[~2020-05-04 5:27 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-01 20:51 [Bug sanitizer/94910] New: " rafael at espindo dot la 2020-05-04 5:27 ` marxin at gcc dot gnu.org [this message] 2020-05-15 11:31 ` [Bug sanitizer/94910] " marxin at gcc dot gnu.org 2020-05-15 16:28 ` rafael at espindo dot la 2020-05-18 9:11 ` marxin at gcc dot gnu.org 2020-05-18 9:12 ` marxin at gcc dot gnu.org 2020-05-18 10:39 ` jakub at gcc dot gnu.org 2020-05-19 13:26 ` marxin at gcc dot gnu.org 2020-05-19 21:05 ` rafael at espindo dot la 2020-05-20 9:11 ` marxin at gcc dot gnu.org 2020-05-25 8:32 ` marxin at gcc dot gnu.org 2020-06-10 11:19 ` cvs-commit at gcc dot gnu.org 2020-06-10 11:20 ` marxin at gcc dot gnu.org 2020-06-12 8:03 ` cvs-commit at gcc dot gnu.org 2020-06-12 8:17 ` cvs-commit at gcc dot gnu.org 2020-06-12 8:30 ` cvs-commit at gcc dot gnu.org 2020-06-12 8:30 ` marxin 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-94910-4-L02F6Mypi1@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).