public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/101885] [10/11/12 Regression] wrong code at -O3 on x86_64-linux-gnu Date: Thu, 20 Jan 2022 18:00:39 +0000 [thread overview] Message-ID: <bug-101885-4-mKSmr0jFcT@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101885-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101885 --- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> --- For instructions that inherently set a condition code register, the @code{compare} operator is always written as the first RTL expression of the @code{parallel} instruction pattern. For example, @smallexample (define_insn "" [(set (reg:CCZ FLAGS_REG) (compare:CCZ (plus:SI (match_operand:SI 1 "register_operand" "%r") (match_operand:SI 2 "register_operand" "r")) (const_int 0))) (set (match_operand:SI 0 "register_operand" "=r") (plus:SI (match_dup 1) (match_dup 2)))] "" "addl %0, %1, %2") @end smallexample see the https://gcc.gnu.org/pipermail/gcc-patches/2017-May/thread.html#474080 thread.
next prev parent reply other threads:[~2022-01-20 18:00 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-12 17:09 [Bug tree-optimization/101885] New: " qrzhang at gatech dot edu 2021-08-12 17:10 ` [Bug tree-optimization/101885] " qrzhang at gatech dot edu 2021-08-12 21:06 ` [Bug rtl-optimization/101885] [10/11/12 Regression] " pinskia at gcc dot gnu.org 2021-08-12 21:22 ` pinskia at gcc dot gnu.org 2021-08-12 21:23 ` pinskia at gcc dot gnu.org 2021-08-16 7:34 ` rguenth at gcc dot gnu.org 2022-01-20 15:29 ` jakub at gcc dot gnu.org 2022-01-20 15:40 ` jakub at gcc dot gnu.org 2022-01-20 16:55 ` jakub at gcc dot gnu.org 2022-01-20 17:15 ` jakub at gcc dot gnu.org 2022-01-20 17:27 ` jakub at gcc dot gnu.org 2022-01-20 17:29 ` jakub at gcc dot gnu.org 2022-01-20 18:00 ` jakub at gcc dot gnu.org [this message] 2022-02-03 11:07 ` roger at nextmovesoftware dot com 2022-02-04 1:03 ` segher at gcc dot gnu.org 2022-02-04 9:38 ` cvs-commit at gcc dot gnu.org 2022-02-10 22:26 ` [Bug rtl-optimization/101885] [10/11 " roger at nextmovesoftware dot com 2022-03-16 7:37 ` roger at nextmovesoftware dot com 2022-03-16 8:10 ` rguenth at gcc dot gnu.org 2022-06-28 10:46 ` jakub at gcc dot gnu.org 2023-07-07 10:40 ` [Bug rtl-optimization/101885] [11 " 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-101885-4-mKSmr0jFcT@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).