public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/99930] Failure to optimize floating point -abs(x) in nontrivial code at -O2/3 Date: Tue, 06 Apr 2021 12:00:25 +0000 [thread overview] Message-ID: <bug-99930-4-6mQi454DzE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99930-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99930 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |segher at gcc dot gnu.org --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- Seems because of r93 being live: insn_cost 8 for 9: r93:V4SF=[`*.LC0'] REG_EQUAL const_vector insn_cost 4 for 10: {r91:SF=abs(r92:SF);use r93:V4SF;clobber flags:CC;} REG_DEAD r92:SF REG_UNUSED flags:CC insn_cost 8 for 11: r95:V4SF=[`*.LC1'] REG_EQUAL const_vector insn_cost 4 for 12: {r94:SF=-r91:SF;use r95:V4SF;clobber flags:CC;} REG_DEAD r91:SF REG_UNUSED flags:CC insn_cost 4 for 13: flags:CCFP=cmp(r90:SF,r94:SF) REG_DEAD r94:SF insn_cost 12 for 14: pc={(flags:CCFP>0)?L35:pc} REG_DEAD flags:CCFP REG_BR_PROB 59055804 insn_cost 8 for 16: r97:SF=[r89:DI+0x4] REG_DEAD r89:DI insn_cost 4 for 18: {r96:SF=abs(r97:SF);use r93:V4SF;clobber flags:CC;} REG_DEAD r97:SF REG_DEAD r93:V4SF REG_UNUSED flags:CC insn_cost 4 for 20: {r99:SF=-r96:SF;use r95:V4SF;clobber flags:CC;} REG_DEAD r96:SF REG_DEAD r95:V4SF REG_UNUSED flags:CC while at -O1 we have two loads of LC0 and r93 is dead after insn 10.
next prev parent reply other threads:[~2021-04-06 12:00 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-06 10:38 [Bug target/99930] New: " core13 at gmx dot net 2021-04-06 11:57 ` [Bug rtl-optimization/99930] " rguenth at gcc dot gnu.org 2021-04-06 12:00 ` rguenth at gcc dot gnu.org [this message] 2021-04-06 17:31 ` segher at gcc dot gnu.org 2021-04-07 10:04 ` jakub at gcc dot gnu.org 2021-04-07 10:06 ` jakub at gcc dot gnu.org 2021-04-07 10:14 ` ubizjak at gmail dot com 2021-04-07 10:27 ` crazylht at gmail dot com 2021-04-07 16:32 ` segher at gcc dot gnu.org 2021-04-08 9:48 ` crazylht at gmail dot com 2021-04-08 22:46 ` segher at gcc dot gnu.org 2021-07-25 1:30 ` pinskia at gcc dot gnu.org 2023-12-24 23:16 ` [Bug middle-end/99930] " 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-99930-4-6mQi454DzE@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).