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:23:51 +0000	[thread overview]
Message-ID: <bug-27227-131-puhKOJaibL@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 #5 from Adam Stylinski <kungfujesus06 at gmail dot com> ---
Apologies for my ignorance by the way, I've been mostly spoiled lately with x86
and aarch64 which handle this to some degree for you in the uarch.  I wrote
this code a long time ago when I was just getting familiar with Altivec, so I'm
well aware what I was doing could have been completely wrong and/or stupid.  At
the very least I could have done more to pipeline the unaligned loads so that
the previous vector load for the second half was reused (I don't think GCC can
do this for me).  

I'm hoping people who are intimately familiar with the ABI and heap layout of
big endian POWER4 can clarify if I'm wrong, the library is wrong, or both.

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

      parent reply	other threads:[~2021-01-22 22:23 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
2021-01-22 22:23 ` kungfujesus06 at gmail dot com [this message]

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-puhKOJaibL@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).