This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug tree-optimization/44183] Vectorizer may generate invalid memory access
- From: "rguenth at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 31 Jan 2011 10:06:49 +0000
- Subject: [Bug tree-optimization/44183] Vectorizer may generate invalid memory access
- Auto-submitted: auto-generated
- References: <bug-44183-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44183
--- Comment #7 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-01-31 10:06:27 UTC ---
(In reply to comment #6)
> It depends on the specific values of (a) array end alignment and (b) the number
> of bytes read. As long as the array end + number of bytes read can cross a page
> boundary, you're potentially causing SEGV or other errors.
I don't think this can happen. The access to the out-of-bounds area only
happens if there are pieces inluded in the last (aligned) vector move.
That vector move will be aligned so it can't cross page-boundary. As
it contains at least one allocated element the access may not trap.