public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pthaugen at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/65010] ppc backend generates unnecessary signed extension Date: Thu, 20 Jan 2022 17:48:14 +0000 [thread overview] Message-ID: <bug-65010-4-3RbgyGaG2M@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65010-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65010 pthaugen at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pthaugen at gcc dot gnu.org --- Comment #11 from pthaugen at gcc dot gnu.org --- Another example to clean up. The back to back constant load/sign extend sequence of rtl insns is created in each block by the block reordering pass (.bbo) duplicating the common return block. int foo(int in) { if (in == 1) return 123; return 0; } foo: .LFB0: .cfi_startproc cmpwi 0,3,1 beq 0,.L5 li 3,0 extsw 3,3 blr .p2align 4,,15 .L5: li 3,123 extsw 3,3 blr
next prev parent reply other threads:[~2022-01-20 17:48 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-11 1:21 [Bug target/65010] New: " carrot at google dot com 2015-02-24 23:18 ` [Bug target/65010] " msebor at gcc dot gnu.org 2015-03-06 19:11 ` law at redhat dot com 2015-03-06 22:47 ` msebor at gcc dot gnu.org 2015-03-21 22:23 ` dje at gcc dot gnu.org 2020-06-19 16:42 ` wschmidt at gcc dot gnu.org 2022-01-20 17:48 ` pthaugen at gcc dot gnu.org [this message] 2023-03-23 15:20 ` bergner at gcc dot gnu.org 2023-04-11 17:08 ` aagarwa at gcc dot gnu.org 2024-02-29 21:47 ` segher 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-65010-4-3RbgyGaG2M@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).