public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/65369] [5 Regression] nettle test failure on powerpc64le-linux-gnu when built with -O3 Date: Thu, 12 Mar 2015 15:22:00 -0000 [thread overview] Message-ID: <bug-65369-4-fkaCxKkufa@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65369-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65369 --- Comment #17 from Jakub Jelinek <jakub at gcc dot gnu.org> --- I've tried to add __builtin_memset(ctx, 0, sizeof (*ctx)); to the beginning of md4_init and it changes the result of the program at -O0, so I expect the testcase relies on some particular pattern of uninitialized data in ctx->block.
next prev parent reply other threads:[~2015-03-12 15:22 UTC|newest] Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-09 23:14 [Bug target/65369] New: " doko at gcc dot gnu.org 2015-03-09 23:24 ` [Bug target/65369] " pinskia at gcc dot gnu.org 2015-03-10 9:00 ` rguenth at gcc dot gnu.org 2015-03-10 15:01 ` law at redhat dot com 2015-03-10 21:56 ` msebor at gcc dot gnu.org 2015-03-11 4:04 ` msebor at gcc dot gnu.org 2015-03-11 4:10 ` doko at gcc dot gnu.org 2015-03-11 21:36 ` msebor at gcc dot gnu.org 2015-03-12 2:50 ` msebor at gcc dot gnu.org 2015-03-12 11:11 ` thopre01 at gcc dot gnu.org 2015-03-12 11:11 ` trippels at gcc dot gnu.org 2015-03-12 11:11 ` thopre01 at gcc dot gnu.org 2015-03-12 11:11 ` trippels at gcc dot gnu.org 2015-03-12 11:11 ` thopre01 at gcc dot gnu.org 2015-03-12 13:54 ` amodra at gmail dot com 2015-03-12 14:01 ` amodra at gmail dot com 2015-03-12 14:04 ` trippels at gcc dot gnu.org 2015-03-12 15:10 ` jakub at gcc dot gnu.org 2015-03-12 15:22 ` jakub at gcc dot gnu.org [this message] 2015-03-12 15:34 ` trippels at gcc dot gnu.org 2015-03-12 15:38 ` jakub at gcc dot gnu.org 2015-03-12 15:40 ` msebor at gcc dot gnu.org 2015-03-12 15:42 ` jakub at gcc dot gnu.org 2015-03-12 15:44 ` trippels at gcc dot gnu.org 2015-03-12 15:48 ` jakub at gcc dot gnu.org 2015-03-12 15:54 ` msebor at gcc dot gnu.org 2015-03-12 16:32 ` trippels at gcc dot gnu.org 2015-03-13 4:42 ` thopre01 at gcc dot gnu.org 2015-03-13 6:38 ` amodra at gmail dot com 2015-03-13 6:46 ` trippels at gcc dot gnu.org 2015-03-13 9:46 ` rguenth at gcc dot gnu.org 2015-03-13 14:01 ` amodra at gmail dot com 2015-03-13 14:22 ` amodra at gmail dot com 2015-03-13 14:51 ` trippels at gcc dot gnu.org 2015-03-13 15:25 ` wschmidt at gcc dot gnu.org 2015-03-13 16:25 ` jakub at gcc dot gnu.org 2015-03-13 16:45 ` jakub at gcc dot gnu.org 2015-03-13 16:46 ` jakub at gcc dot gnu.org 2015-03-14 9:57 ` jakub at gcc dot gnu.org 2015-03-14 9:57 ` jakub 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-65369-4-fkaCxKkufa@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: linkBe 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).