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 ipa/114698] [12/13/14 regression] dcfldd produces wrong sha256 sum on ppc64le and -O3 since r12-5244-g64f3e71c302b4a
Date: Thu, 11 Apr 2024 19:06:42 +0000 [thread overview]
Message-ID: <bug-114698-4-CJCVrPzuHh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114698-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114698
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #3)
> uint8_t buffer[SHA256_BLOCK_LENGTH];
>
> W256 = (sha2_word32*)context->buffer;
>
> This is starting to smell like the code is violating strict aliasing rules
> ...
The patch in https://github.com/NetBSD/pkgsrc/issues/122 applies directly
here too.
next prev parent reply other threads:[~2024-04-11 19:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 18:36 [Bug target/114698] New: dcfldd produces wrong sha256 sum on ppc64le and -O3 bergner at gcc dot gnu.org
2024-04-11 18:38 ` [Bug target/114698] " bergner at gcc dot gnu.org
2024-04-11 18:45 ` [Bug ipa/114698] " bergner at gcc dot gnu.org
2024-04-11 18:52 ` [Bug ipa/114698] [12/13/14 regression] dcfldd produces wrong sha256 sum on ppc64le and -O3 since r12-5244-g64f3e71c302b4a pinskia at gcc dot gnu.org
2024-04-11 19:06 ` pinskia at gcc dot gnu.org [this message]
2024-04-11 19:07 ` pinskia at gcc dot gnu.org
2024-04-11 19:08 ` pinskia at gcc dot gnu.org
2024-04-11 19:09 ` pinskia at gcc dot gnu.org
2024-04-11 19:18 ` bergner at gcc dot gnu.org
2024-04-11 19:25 ` bergner at gcc dot gnu.org
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-114698-4-CJCVrPzuHh@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).