From: Peter Bergner <bergner@linux.ibm.com>
To: Surya Kumari Jangala <jskumari@linux.vnet.ibm.com>,
Ajit Agarwal <aagarwa1@linux.ibm.com>,
gcc-patches <gcc-patches@gcc.gnu.org>
Cc: Segher Boessenkool <segher@kernel.crashing.org>
Subject: Re: [PATCH] rs6000: suboptimal code for returning bool value on target ppc
Date: Fri, 17 Mar 2023 16:20:54 -0500 [thread overview]
Message-ID: <4bd74349-4ce3-515f-3ddd-37698639130e@linux.ibm.com> (raw)
In-Reply-To: <38952348-21a7-c275-a2f7-3a0abbca7c9d@linux.vnet.ibm.com>
On 3/16/23 10:37 PM, Surya Kumari Jangala wrote:
> The issue of suboptimal code exists even for integer return value and not just bool return value. See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103784#c9
> So the patch would need to take care of integer return values too.
Correct. Basically any time we return an integral type (signed or unsigned)
type is smaller than the hard register we are returning it in, we can get these
unwanted sign/zero extensions.
I'm sure we have quite a few bugzillas mentioning the unneeded sign/zero extends.
Peter
next prev parent reply other threads:[~2023-03-17 21:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 5:20 Ajit Agarwal
2023-03-16 7:40 ` Richard Biener
2023-03-16 8:11 ` Ajit Agarwal
2023-03-16 8:14 ` Richard Biener
2023-03-16 8:19 ` Ajit Agarwal
2023-03-16 9:52 ` Richard Biener
2023-03-16 10:11 ` Ajit Agarwal
2023-03-16 10:30 ` Richard Biener
2023-03-16 10:43 ` Ajit Agarwal
2023-03-16 10:56 ` Richard Biener
2023-03-16 11:43 ` Ajit Agarwal
2023-03-16 14:48 ` Jeff Law
2023-03-17 11:49 ` Ajit Agarwal
2023-03-17 3:37 ` Surya Kumari Jangala
2023-03-17 21:20 ` Peter Bergner [this message]
2023-03-18 3:53 ` Peter Bergner
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=4bd74349-4ce3-515f-3ddd-37698639130e@linux.ibm.com \
--to=bergner@linux.ibm.com \
--cc=aagarwa1@linux.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jskumari@linux.vnet.ibm.com \
--cc=segher@kernel.crashing.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: link
Be 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).