public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "piliu at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/105134] New: tree-vectorize produces error code Date: Sat, 02 Apr 2022 02:43:43 +0000 [thread overview] Message-ID: <bug-105134-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105134 Bug ID: 105134 Summary: tree-vectorize produces error code Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: piliu at redhat dot com Target Milestone: --- On x86_64, kexec-tools built with gcc-12 can not boot the 2nd kernel successfully. After debugging, it turns out to be related with "tree-vectorize" option. As kexec-tools commit 1b03cf7 purgatory: do not enable vectorization automatically for purgatory compiling. I have no idea about what happens, but it seems to be related with the generation of the code piece void sha256_starts( sha256_context *ctx ) { ctx->total[0] = 0; ctx->total[1] = 0; ctx->state[0] = 0x6A09E667; ctx->state[1] = 0xBB67AE85; ctx->state[2] = 0x3C6EF372; ctx->state[3] = 0xA54FF53A; ctx->state[4] = 0x510E527F; ctx->state[5] = 0x9B05688C; ctx->state[6] = 0x1F83D9AB; ctx->state[7] = 0x5BE0CD19; }
next reply other threads:[~2022-04-02 2:43 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-02 2:43 piliu at redhat dot com [this message] 2022-04-02 3:01 ` [Bug c/105134] " piliu at redhat dot com 2022-04-02 5:28 ` piliu at redhat dot com 2022-04-04 7:15 ` rguenth at gcc dot gnu.org 2022-04-06 2:12 ` piliu at redhat dot com 2022-04-06 2:14 ` piliu at redhat dot com 2022-04-06 2:17 ` piliu at redhat dot com 2022-11-25 22:53 ` pinskia at gcc dot gnu.org 2022-11-25 23:00 ` pinskia at gcc dot gnu.org 2022-11-25 23:03 ` pinskia at gcc dot gnu.org 2022-11-30 3:32 ` piliu at redhat dot com 2022-11-30 3:42 ` pinskia at gcc dot gnu.org 2024-02-21 0:40 ` [Bug tree-optimization/105134] " pinskia 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-105134-4@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).