public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikpe at it dot uu dot se" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/44183] Vectorizer may generate invalid memory access
Date: Thu, 20 May 2010 10:18:00 -0000 [thread overview]
Message-ID: <20100520101838.27867.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44183-682@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from mikpe at it dot uu dot se 2010-05-20 10:18 -------
(In reply to comment #3)
> I am curious what is the problem with that? These elements are not used, they
> are just loaded...
An out-of-bounds read can result in a SEGV if the memory is unmapped. Worse
things can happen if the memory is "special" (think kernels and MMIO).
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44183
next prev parent reply other threads:[~2010-05-20 10:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 1:22 [Bug tree-optimization/44183] New: " hjl dot tools at gmail dot com
2010-05-20 7:14 ` [Bug tree-optimization/44183] " irar at il dot ibm dot com
2010-05-20 8:51 ` hjl dot tools at gmail dot com
2010-05-20 10:05 ` irar at il dot ibm dot com
2010-05-20 10:18 ` mikpe at it dot uu dot se [this message]
2010-05-20 10:24 ` irar at il dot ibm dot com
2010-05-20 11:07 ` mikpe at it dot uu dot se
[not found] <bug-44183-4@http.gcc.gnu.org/bugzilla/>
2011-01-31 10:28 ` rguenth at gcc dot gnu.org
2011-01-31 11:36 ` rguenth 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=20100520101838.27867.qmail@sourceware.org \
--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).