public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/67446] libiberty sha1.c:324 sanitizer runtime error: load of misaligned address 0x62f00011847e for type 'const sha1_uint32', which requires 4 byte alignment
Date: Fri, 04 Sep 2015 07:44:00 -0000	[thread overview]
Message-ID: <bug-67446-4-GxdfhDaMt5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67446-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67446

--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Mikhail Maltsev from comment #2)
> BTW, a similar bug reproduces during GCC bootstrap with ubsan:
> 
> /home/jenkins/workspace/ubsan-bootstrap/src/libiberty/md5.c:336:7: runtime
> error: load of misaligned address 0x7fff91f9983a for type 'const
> md5_uint32', which requires 4 byte alignment
> 0x7fff91f9983a: note: pointer points here
>  00 00  f4 48 00 00 00 00 00 00  0a 00 00 00 0e 00 00 00  0d 01 00 00 00 00
> 00 00  07 49 00 00 00 00
>               ^

But those are two different issues.  Also the md5 code explicitly checks to see
if unaligned loads are supported though, it could be better about it.  Please
file this as a separate bug and also note both of these functions really come
from glibc so you might want to file it there (but there might be another
upstream code too).


      parent reply	other threads:[~2015-09-04  7:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-04  6:13 [Bug other/67446] New: " zeccav at gmail dot com
2015-09-04  6:41 ` [Bug other/67446] " pinskia at gcc dot gnu.org
2015-09-04  7:40 ` miyuki at gcc dot gnu.org
2015-09-04  7:44 ` pinskia at gcc dot gnu.org [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-67446-4-GxdfhDaMt5@http.gcc.gnu.org/bugzilla/ \
    --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).