public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mikpelinux at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/108657] [13 Regression] csmith: possible wrong checksum with -O3 and -ftrivial-auto-var-init=zero Date: Tue, 07 Feb 2023 18:01:32 +0000 [thread overview] Message-ID: <bug-108657-4-hbvkLH3owq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108657-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108657 --- Comment #11 from Mikael Pettersson <mikpelinux at gmail dot com> --- Bisected on x86_64-linux-gnu: dc477ffb4aba21e9cf47de22a4df6f2b23849505 is the first bad commit commit dc477ffb4aba21e9cf47de22a4df6f2b23849505 Author: Richard Biener <rguenther@suse.de> Date: Thu Jul 21 10:13:46 2022 +0200 tree-optimization/106378 - DSE of LEN_STORE and MASK_STORE The following enhances DSE to handle LEN_STORE (optimally) and MASK_STORE (conservatively). PR tree-optimization/106378 * tree-ssa-dse.cc (initialize_ao_ref_for_dse): Handle LEN_STORE, add mode to initialize a may-def and handle MASK_STORE that way. (dse_optimize_stmt): Query may-defs. Handle internal functions LEN_STORE and MASK_STORE similar to how we handle memory builtins but without byte tracking.
next prev parent reply other threads:[~2023-02-07 18:01 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-03 13:59 [Bug c/108657] New: " dcb314 at hotmail dot com 2023-02-03 16:27 ` [Bug c/108657] " dcb314 at hotmail dot com 2023-02-03 18:15 ` [Bug middle-end/108657] " pinskia at gcc dot gnu.org 2023-02-03 18:41 ` dcb314 at hotmail dot com 2023-02-03 18:47 ` pinskia at gcc dot gnu.org 2023-02-04 12:01 ` dcb314 at hotmail dot com 2023-02-04 12:17 ` dcb314 at hotmail dot com 2023-02-04 12:31 ` dcb314 at hotmail dot com 2023-02-06 13:37 ` dcb314 at hotmail dot com 2023-02-06 16:59 ` dcb314 at hotmail dot com 2023-02-06 17:32 ` dcb314 at hotmail dot com 2023-02-06 20:28 ` [Bug middle-end/108657] [13 Regression] " pinskia at gcc dot gnu.org 2023-02-07 18:01 ` mikpelinux at gmail dot com [this message] 2023-02-08 8:42 ` dcb314 at hotmail dot com 2023-02-14 14:53 ` dcb314 at hotmail dot com 2023-02-14 21:09 ` dcb314 at hotmail dot com 2023-02-15 18:22 ` jakub at gcc dot gnu.org 2023-02-15 18:29 ` jakub at gcc dot gnu.org 2023-02-15 18:43 ` jakub at gcc dot gnu.org 2023-02-15 18:48 ` pinskia at gcc dot gnu.org 2023-02-15 18:56 ` jakub at gcc dot gnu.org 2023-02-15 19:04 ` jakub at gcc dot gnu.org 2023-02-15 19:15 ` jakub at gcc dot gnu.org 2023-02-15 19:32 ` jakub at gcc dot gnu.org 2023-02-16 14:35 ` cvs-commit at gcc dot gnu.org 2023-02-27 10:17 ` rguenth 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-108657-4-hbvkLH3owq@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).