public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jeffreyalaw at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/106679] [13 regression] gcc.dg/tree-prof/cmpsf-1.c fails after r13-2098-g5adfb6540db95d Date: Wed, 28 Sep 2022 00:00:10 +0000 [thread overview] Message-ID: <bug-106679-4-qYM3sJTlro@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106679-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106679 Jeffrey A. Law <jeffreyalaw at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeffreyalaw at gmail dot com --- Comment #5 from Jeffrey A. Law <jeffreyalaw at gmail dot com> --- I think we should probably xfail. That way if/when we fix the profile updating bits for the new copier cmpsf-1.c will test those bits.
next prev parent reply other threads:[~2022-09-28 0:00 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-106679-4@http.gcc.gnu.org/bugzilla/> 2022-08-31 17:29 ` pinskia at gcc dot gnu.org 2022-09-28 0:00 ` jeffreyalaw at gmail dot com [this message] 2022-10-05 10:17 ` cvs-commit at gcc dot gnu.org 2022-10-05 10:17 ` marxin 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-106679-4-qYM3sJTlro@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).