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 tree-optimization/94187] valgrind error in count_nonzero_bytes ? Date: Mon, 16 Mar 2020 10:51:05 +0000 [thread overview] Message-ID: <bug-94187-4-CJKjiHOmKM@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94187-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94187 Martin Liška <marxin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marxin at gcc dot gnu.org Last reconfirmed| |2020-03-16 Ever confirmed|0 |1 Status|UNCONFIRMED |WAITING --- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> --- I can't confirm that with current master with valgrind. Similarly -fsanitize=address is also fine.
next prev parent reply other threads:[~2020-03-16 10:51 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-16 8:10 [Bug c/94187] New: " dcb314 at hotmail dot com 2020-03-16 10:51 ` marxin at gcc dot gnu.org [this message] 2020-03-16 11:18 ` [Bug tree-optimization/94187] " dcb314 at hotmail dot com 2020-03-16 11:20 ` jakub at gcc dot gnu.org 2020-03-16 11:28 ` jakub at gcc dot gnu.org 2020-03-16 11:35 ` [Bug tree-optimization/94187] [10 Regression] valgrind error in count_nonzero_bytes since r10-2101 jakub at gcc dot gnu.org 2020-03-16 11:40 ` jakub at gcc dot gnu.org 2020-03-16 12:07 ` dcb314 at hotmail dot com 2020-03-16 21:04 ` dcb314 at hotmail dot com 2020-03-17 8:38 ` marxin at gcc dot gnu.org 2020-03-17 8:52 ` dcb314 at hotmail dot com 2020-03-17 9:44 ` cvs-commit at gcc dot gnu.org 2020-03-17 9:54 ` jakub at gcc dot gnu.org 2020-03-25 16:08 ` dcb314 at hotmail dot com
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-94187-4-CJKjiHOmKM@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).