public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/58517] ifcvt (after combine) puts ccreg clobbering insn between ccset insn and ccreg use Date: Fri, 02 Jun 2023 01:44:35 +0000 [thread overview] Message-ID: <bug-58517-4-7XrYULZuec@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-58517-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58517 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed|2013-10-05 00:00:00 |2023-6-1 --- Comment #10 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Note the wrong code can be still reproduced in GCC 13 too.
next prev parent reply other threads:[~2023-06-02 1:44 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-09-23 21:50 [Bug target/58517] New: [SH] wrong code with subc and movsicc (-mpretend-cmove) after ce2 olegendo at gcc dot gnu.org 2013-10-05 20:22 ` [Bug rtl-optimization/58517] icvt (after combine) puts ccreg clobbering insn between ccset insn and cc use olegendo at gcc dot gnu.org 2013-10-05 21:16 ` [Bug rtl-optimization/58517] icvt (after combine) puts ccreg clobbering insn between ccset insn and ccreg use olegendo at gcc dot gnu.org 2013-10-05 22:17 ` olegendo at gcc dot gnu.org 2013-10-05 23:23 ` steven at gcc dot gnu.org 2015-09-11 11:12 ` [Bug rtl-optimization/58517] ifcvt " ktkachov at gcc dot gnu.org 2023-06-02 1:38 ` pinskia at gcc dot gnu.org 2023-06-02 1:43 ` pinskia at gcc dot gnu.org 2023-06-02 1:44 ` pinskia at gcc dot gnu.org [this message] 2023-06-02 7:28 ` pinskia at gcc dot gnu.org 2023-06-02 7:57 ` pinskia at gcc dot gnu.org 2023-06-03 8:58 ` olegendo at gcc dot gnu.org 2023-06-03 9:02 ` pinskia at gcc dot gnu.org 2023-06-03 21:50 ` pinskia at gcc dot gnu.org 2023-06-03 22:18 ` pinskia at gcc dot gnu.org 2023-06-03 22:23 ` olegendo at gcc dot gnu.org 2023-06-03 22:59 ` pinskia at gcc dot gnu.org 2023-06-04 0:48 ` 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-58517-4-7XrYULZuec@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).