http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44183
--- Comment #7 from Richard Guenther 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 cr
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44183
Richard Guenther changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|
--- Comment #1 from irar at il dot ibm dot com 2010-05-20 07:13 ---
Do you mean that extract_even implementation does something illegal with this
last element? Misaligned load also accesses elements outside the array, but the
problem is in extract_even?
Other than doing something in the
--- Comment #2 from hjl dot tools at gmail dot com 2010-05-20 08:50 ---
(In reply to comment #1)
> Do you mean that extract_even implementation does something illegal with this
> last element? Misaligned load also accesses elements outside the array, but
> the
> problem is in extract_ev
--- Comment #3 from irar at il dot ibm dot com 2010-05-20 10:04 ---
I am curious what is the problem with that? These elements are not used, they
are just loaded...
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44183
--- 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
--- Comment #5 from irar at il dot ibm dot com 2010-05-20 10:24 ---
Even if we are talking about less than vector size from array boundary? And
that boundary is not (vector) aligned.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44183
--- Comment #6 from mikpe at it dot uu dot se 2010-05-20 11:05 ---
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.
