public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "carrot at google dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/65010] New: ppc backend generates unnecessary signed extension Date: Wed, 11 Feb 2015 01:21:00 -0000 [thread overview] Message-ID: <bug-65010-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65010 Bug ID: 65010 Summary: ppc backend generates unnecessary signed extension Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: carrot at google dot com Target: powerpc64le I use ppc gcc to compile following code with option -O2 unsigned long c2l(unsigned char* p) { unsigned long res = *p + *(p+1); return res; } long c2sl(signed char* p) { long res = *p + *(p+1); return res; } Trunk gcc generates: c2l: lbz 10,0(3) lbz 9,1(3) add 3,10,9 extsw 3,3 blr c2sl: lbz 9,1(3) lbz 10,0(3) extsb 9,9 extsb 3,10 add 3,3,9 extsw 3,3 blr The extsw instructions in both functions are unnecessary since it can't change the value in return register.
next reply other threads:[~2015-02-11 1:21 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-11 1:21 carrot at google dot com [this message] 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 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@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).