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/48986] Missed optimization in atomic decrement on x86/x64 Date: Mon, 16 May 2011 12:07:00 -0000 [thread overview] Message-ID: <bug-48986-4-5OJAPWWjl4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-48986-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48986 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEW CC| |uros at gcc dot gnu.org AssignedTo|jakub at gcc dot gnu.org |unassigned at gcc dot | |gnu.org --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-05-16 11:26:51 UTC --- On: int foo (int *p) { return __sync_fetch_and_add (p, -1) == 1; } int bar (int *p) { return __sync_add_and_fetch (p, -1) == 0; } I get better generated code for the second routine if I do: --- gcc/config/i386/sync.md.jj 72010-05-21 11:46:29.000000000 +0200 +++ gcc/config/i386/sync.md 2011-05-16 13:06:13.000000000 +0200 @@ -170,7 +170,7 @@ [(match_operand:SWI 1 "memory_operand" "+m")] UNSPECV_XCHG)) (set (match_dup 1) (plus:SWI (match_dup 1) - (match_operand:SWI 2 "register_operand" "0"))) + (match_operand:SWI 2 "nonmemory_operand" "0"))) (clobber (reg:CC FLAGS_REG))] "TARGET_XADD" "lock{%;} xadd{<imodesuffix>}\t{%0, %1|%1, %0}") and for foo identical code, so maybe that change is always beneficial, allowing combiner and other early RTL passes to see there a constant instead of a REG. Unfortunately, even with this change the combiner doesn't attempt to combine this pattern with the following cmpsi_1 pattern, supposedly because sync_old_addsi pattern isn't single_set. I guess we could handle this during expansion, but it would be a mess, or some other pass (e.g. peephole2 or something similar). peephole2 might kind of too late though, by that time the constant must be loaded already into some register, so we'd need to peephole2 3 insns, where the load of the constant might often not be the first one.
next prev parent reply other threads:[~2011-05-16 11:39 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-05-13 10:32 [Bug rtl-optimization/48986] New: " piotr.wyderski at gmail dot com 2011-05-13 15:07 ` [Bug rtl-optimization/48986] " jakub at gcc dot gnu.org 2011-05-16 12:07 ` jakub at gcc dot gnu.org [this message] 2011-05-16 13:14 ` [Bug target/48986] " jakub at gcc dot gnu.org 2011-05-17 7:58 ` jakub at gcc dot gnu.org 2011-05-17 8:17 ` jakub at gcc dot gnu.org 2011-05-17 8:41 ` jakub at gcc dot gnu.org 2021-07-26 5:22 ` 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-48986-4-5OJAPWWjl4@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).