public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tetra2005 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/61547] Invalid sanitization of trailing byte in __builtin_strlen Date: Thu, 19 Jun 2014 20:09:00 -0000 [thread overview] Message-ID: <bug-61547-4-cUgsy6S174@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61547-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61547 Yuri Gribov <tetra2005 at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tetra2005 at gmail dot com --- Comment #5 from Yuri Gribov <tetra2005 at gmail dot com> --- Yeah, GCC is different in this regard.
next prev parent reply other threads:[~2014-06-19 20:09 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-06-18 9:52 [Bug sanitizer/61547] New: " y.gribov at samsung dot com 2014-06-18 9:54 ` [Bug sanitizer/61547] " y.gribov at samsung dot com 2014-06-18 10:37 ` kcc at gcc dot gnu.org 2014-06-18 11:19 ` rguenth at gcc dot gnu.org 2014-06-18 11:33 ` kcc at gcc dot gnu.org 2014-06-19 20:09 ` tetra2005 at gmail dot com [this message] 2014-10-16 13:47 ` ygribov at gcc dot gnu.org 2015-04-17 7:45 ` y.gribov at samsung 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-61547-4-cUgsy6S174@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).