public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kungfujesus06 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug malloc/27227] Memory corruption for altivec unaligned load / store
Date: Fri, 22 Jan 2021 22:20:23 +0000	[thread overview]
Message-ID: <bug-27227-131-NSDHntNNwF@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27227-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=27227

--- Comment #4 from Adam Stylinski <kungfujesus06 at gmail dot com> ---
It can be but not in the current test scenario I have.  Doing vec_ld(15, ptr)
for the second half essentially means that the load will never span outside the
heap in the even that the address just so happens to be aligned, no?

Basically the final unaligned loads in the last column are triggering asan and
in general are causing issues.  I suspect the logic for unaligned stores are
causing similar grief.  I _thought_ I had been doing exactly what Apple had
mentioned here:

> Typically this means that a looping function will have to stop one loop iteration before it reaches the end of the data run, and handle the last few bytes in special case code. 

Is this now broken or had I been doing the remainder peeling incorrectly all
along?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2021-01-22 22:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-22 17:45 [Bug malloc/27227] New: " kungfujesus06 at gmail dot com
2021-01-22 18:11 ` [Bug malloc/27227] " schwab@linux-m68k.org
2021-01-22 18:21 ` kungfujesus06 at gmail dot com
2021-01-22 20:36 ` fweimer at redhat dot com
2021-01-22 22:20 ` kungfujesus06 at gmail dot com [this message]
2021-01-22 22:23 ` kungfujesus06 at gmail 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-27227-131-NSDHntNNwF@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.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).