public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/47311] [4.6 Regression][C++0x] ICE in tsubst @cp/pt.c:10502 Date: Mon, 17 Jan 2011 19:18:00 -0000 [thread overview] Message-ID: <bug-47311-4-bbmUuDOllr@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-47311-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47311 --- Comment #17 from Richard Henderson <rth at gcc dot gnu.org> 2011-01-17 18:40:05 UTC --- (In reply to comment #16) > ==5267== Invalid read of size 8 > ==5267== at 0x11E4E24: search_line_sse42(unsigned char const*, unsigned It's fine. (1) Note that we've already verified above that the address is aligned and (2) that we will in fact find the end-of-line marker that we expect before we examine data beyond END. I suppose valgrind expects us to update EDX in > 454│ /* Main loop, processing 16 bytes at a time. By doing the whole loop > 455│ in inline assembly, we can make proper use of the flags set. */ > 456│ __asm ( "sub $16, %1\n" > 457│ " .balign 16\n" > 458│ "0: add $16, %1\n" > 459│ " %vpcmpestri $0, (%1), %2\n" > 460│ " jnc 0b" > 461│ : "=&c"(index), "+r"(s) > 462├> : "x"(search), "a"(4), "d"(16)); so that it can tell that we're examining only the first EDX bytes of the value read, but that would require a bit of useless arithmetic here. If there's some easy way we can add a valgrind exception for these functions to the gcc source tree, I'd be open to do so. But I also don't want to figure out how to do that myself.
next prev parent reply other threads:[~2011-01-17 18:40 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-01-15 22:53 [Bug c++/47311] New: [C++0x] " pluto at agmk dot net 2011-01-15 23:16 ` [Bug c++/47311] " hjl.tools at gmail dot com 2011-01-15 23:18 ` hjl.tools at gmail dot com 2011-01-15 23:20 ` pluto at agmk dot net 2011-01-15 23:27 ` pluto at agmk dot net 2011-01-16 0:19 ` pluto at agmk dot net 2011-01-16 0:38 ` pluto at agmk dot net 2011-01-16 1:05 ` hjl.tools at gmail dot com 2011-01-16 1:09 ` pluto at agmk dot net 2011-01-16 1:24 ` pluto at agmk dot net 2011-01-16 1:36 ` [Bug preprocessor/47311] " hjl.tools at gmail dot com 2011-01-16 1:36 ` zsojka at seznam dot cz 2011-01-16 1:53 ` pluto at agmk dot net 2011-01-16 2:04 ` zsojka at seznam dot cz 2011-01-16 3:15 ` pluto at agmk dot net 2011-01-17 16:08 ` [Bug preprocessor/47311] [4.6 Regression][C++0x] " rth at gcc dot gnu.org 2011-01-17 18:39 ` pluto at agmk dot net 2011-01-17 19:18 ` rth at gcc dot gnu.org [this message] 2011-01-17 19:59 ` pluto at agmk dot net 2011-01-17 20:07 ` andi-gcc at firstfloor dot org 2011-01-17 20:09 ` jakub at gcc dot gnu.org 2011-01-18 14:28 ` hjl.tools at gmail dot com 2011-01-18 14:44 ` jakub at gcc dot gnu.org 2011-01-20 10:44 ` dodji at gcc dot gnu.org 2011-01-20 10:47 ` dodji at gcc dot gnu.org 2011-01-20 16:37 ` dodji at gcc dot gnu.org 2011-01-22 13:54 ` pluto at agmk dot net 2011-01-25 23:05 ` dodji at gcc dot gnu.org 2011-01-28 23:01 ` pluto at agmk dot net 2011-01-29 7:07 ` dodji at gcc dot gnu.org 2011-01-29 7:16 ` dodji at gcc dot gnu.org 2011-02-02 18:20 ` dnovillo 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-47311-4-bbmUuDOllr@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).