public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/110829] [13/14 Regression] FAIL: gcc.dg/pr56837.c scan-tree-dump-times optimized "memset ..c, 68, 16384.;" 1 Date: Thu, 27 Jul 2023 10:37:22 +0000 [thread overview] Message-ID: <bug-110829-4-nvKYOv1IcI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110829-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110829 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-13 branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:00c806ea70406e6e67170e51095533dcb8a20cf8 commit r13-7613-g00c806ea70406e6e67170e51095533dcb8a20cf8 Author: Richard Biener <rguenther@suse.de> Date: Thu Jul 27 12:34:34 2023 +0200 XFAIL parts broken deliberately by r13-1762-gf9d4c3b45c5ed5 The following XFAILs recognizing a complex store as memset. PR tree-optimization/110829 * gcc.dg/pr56837.c: XFAIL part of the testcase. (cherry picked from commit 41482832ad0aeaa0e4ae2f8d2beff17023cd00bf)
next prev parent reply other threads:[~2023-07-27 10:37 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-27 10:33 [Bug tree-optimization/110829] New: " rguenth at gcc dot gnu.org 2023-07-27 10:34 ` [Bug tree-optimization/110829] " rguenth at gcc dot gnu.org 2023-07-27 10:36 ` cvs-commit at gcc dot gnu.org 2023-07-27 10:37 ` cvs-commit at gcc dot gnu.org [this message] 2024-03-07 23:28 ` law at gcc dot gnu.org 2024-05-21 9:16 ` [Bug tree-optimization/110829] [13/14/15 " 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-110829-4-nvKYOv1IcI@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).